Skip to main content
Glama

update_skill

Update an existing custom skill (name, description, body, or keywords). Use when refining agent guidance.

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": "update_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyNo
nameNo
keywordsNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description does not need to establish that this is a non-destructive mutation. It adds nothing further on behavior: it does not say whether omitted fields are preserved (patch) or cleared (replace), whether keywords are appended or overwritten, or what permissions are needed.

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?

Two short sentences, front-loaded with the action and the affected fields. The second sentence is somewhat vague but still serves a routing purpose; there is no filler.

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

Completeness2/5

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

This is a 5-parameter mutation tool with zero schema description coverage and no output schema, so the description needs to explain the required id, update semantics, and what the call returns or affects. It covers only which fields can change, leaving the agent under-informed for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must carry the load, but it only restates four property names from the schema. The required `id` parameter is never mentioned, and no field carries added meaning such as format, replace-vs-merge semantics, or constraints on keywords.

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?

The description gives a specific verb and resource ("Update an existing custom skill") and enumerates the mutable fields (name, description, body, keywords), so the agent knows this is a modification rather than a create/delete. It does not explicitly name or contrast with create_skill or delete_skill, leaving sibling disambiguation to the obvious verb difference.

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 refining agent guidance" gives a loose situational cue but no concrete conditions, prerequisites, or exclusions. Nothing tells the agent when to prefer create_skill over this tool, or what to do if the skill does not exist yet.

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