Some MCP clients, such as Claude, use the server description and inject it into the context of the agent. You can edit the server description using the markdown editor on the page and include server-level instructions for the agent.
As an example, you can instruct the agent to always search for the object primary key using the search tool before calling an action that takes the primary key as a parameter.
In order for the agent to be able to read the MCP server description, the agent must be granted read permission on the Developer Console application. Include either the end users connecting to your agents or the service user your agent is using as a viewer to the application in the Sharing & Tokens page.
Use the Agent tool description field in the Ontology Manager application to update the description the agent sees when using the action as a tool. This allows you to provide specific guidance to AI agents about when and how to use each action. For example, an action that creates a new task and gets the project ID for linking the tasks could include instructions on how to obtain the project ID.

Claude skills ↗ are reusable instruction sets that extend what Claude can do. You can integrate Ontology MCP tools with your skills to encode more complex business logic into your agent.
In the example below, a skill named get-or-create-task guides the agent on how to use both the search tool and the create task action tool in combination. This prevents duplicate tasks from being created by first searching for an existing task before creating a new one.
Copied!1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26--- name: get-or-create-task description: Searches for a task by title in a project, returns it if found, or creates a new task if not found --- # Get or create task Find an existing task by title within a project, or create a new task if no match is found. ## Instructions 1. Search for the task by title using the search tool: - Tool: `search-osdk-todo-task` - Filter results by `project_id` if provided 2. Evaluate results: - If a match is found, return the existing task details - If multiple matches are found, use the first match - If no matches are found, proceed to create a new task 3. Create a new task using the create task action tool: - Tool: `create-osdk-todo-task` - Required parameters: `title`, `project_id` - Optional parameters: `description`, `status`, `assigned_to`, `start_date`, `due_date` 4. Return the task details including ID, title, project, status, and assignee
Microsoft Copilot Studio integration only supports authorization code grant in a Confidential Client. This means that when creating the Developer Console application for your Ontology MCP integration with Microsoft Copilot Studio, you should choose Backend service and User's permissions. This will create the required service user that Copilot Studio uses to issue the token on behalf of your users.
See the Palantir DevCon4 presentation and demo for additional examples and guidance on using Ontology MCP.