Skip to main content
Glama

Delete Skill

delete_skill
DestructiveIdempotent

Soft-delete a skill you own (a fork or one you authored from scratch). First-party Gryz Skill Library skills cannot be deleted this way. Version history is retained for audit even after deletion.

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.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is given. The description earns credit for adding soft-delete semantics and audit retention of version history, but says nothing about permission requirements, effect on forks, or error behavior when deleting a non-owned skill.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action and scope before the exception and retention note. No filler, though the retention clause could be merged without loss.

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

Completeness3/5

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

A destructive mutation with no output schema, so the description should carry behavior; it handles ownership scope, soft-delete semantics and retention well but omits permission prerequisites, downstream effects on forks/versions visible to others, and failure modes. Adequate but leaves real gaps for a destructive operation.

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

Parameters3/5

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

There is one parameter with 0% schema description coverage; the schema only encodes a UUID pattern. The description implies the id identifies the owned skill and must refer to a fork or self-authored skill, which adds real meaning, but never explicitly states that the parameter is the skill UUID.

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?

States a precise verb ("Soft-delete") plus resource ("a skill you own") and narrows the scope to forks or skills authored from scratch. It clearly excludes first-party Gryz Skill Library skills, so the agent knows exactly what this operation targets, though it does not name a sibling alternative for the excluded case.

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

Usage Guidelines4/5

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

Gives a clear applicability condition (ownership: fork or self-authored) and an explicit exclusion (first-party library skills "cannot be deleted this way"). The only gap is that it does not say what to do instead when the exclusion applies.

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.