skills_delete
Delete a skill by its unique ID. Removes the skill entry from persistent memory.
Instructions
Delete a Skill.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Delete a skill by its unique ID. Removes the skill entry from persistent memory.
Delete a Skill.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true. The description adds no behavioral context beyond the annotations, such as whether the deletion is reversible or cascading.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise at 4 words, which is efficient but omits necessary context. It is not structured to front-load key information beyond the basic action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete tool with one parameter and no output schema, the description is minimally adequate but fails to explain the parameter's meaning or any side effects, leaving gaps for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, meaning the description provides no explanation for the sole parameter 'id'. The agent cannot determine what identifier should be used (e.g., skill ID, name, or something else).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete a Skill.' clearly states the action and resource, directly matching the tool name. However, it does not differentiate from sibling tools like skills_update or skills_create, which could be confusing in context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. For example, there is no mention that this permanently removes a skill, nor any comparison to skills_update or skills_list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alfredoizdev/contextforge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server