Skip to main content
Glama

delete_skill

Destructive

Permanently delete a custom skill by ID. Use when removing unused tenant skill content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description does add the useful nuance "permanently" (irreversibility) and implies scope limited to custom skills, but it omits what happens on a missing ID, whether built-in skills are rejected, and whether deletion cascades to dependent objects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler; the action and irreversibility are front-loaded ahead of the usage note. Nothing is repeated and nothing needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter destructive tool with annotations covering the safety profile and no output schema, the description covers action, irreversibility, scope, and trigger condition. Only edge-case behavior (not-found, built-in skills, dependent references) is missing, which is minor at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single required parameter, so the description must carry weight; it clarifies that the id refers to a skill identifier and that deletion is by ID. Given only one self-explanatory string parameter, this is close to sufficient, though the ID format (UUID vs slug) is unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Permanently delete a custom skill by ID" states a specific verb, resource, and identifier, and the resource noun ('skill') separates it from the many delete_* siblings. It stops short of naming a sibling or stating explicitly that it only applies to custom (not built-in) skills as a routing rule, so it is clear but not maximally differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when removing unused tenant skill content" supplies a usage context, but it largely restates the purpose (deleting skill content) rather than giving a decision rule. There is no when-not guidance, no mention of alternatives such as update_skill for cleanup, and no note about what to do if the skill is referenced elsewhere.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources