Skip to main content
Glama

get_skill

Read-onlyIdempotent

Get a skill by ID, including its full instruction body. Use when reviewing or editing a skill before attaching it to an agent.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety and repeatability are covered structurally. The description adds real value by disclosing the payload: it returns the full instruction body, which matters for an agent deciding whether the call gives it enough to work with. It does not state behavior for a missing/invalid ID, which keeps it from a 5.

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: the capability is front-loaded with the return payload, then the usage trigger. Every clause carries information and nothing is padded.

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 single-parameter read tool with annotations covering safety and idempotency, plus an explicit statement of what is returned, the definition is essentially self-sufficient. Only error semantics for unknown IDs and where IDs come from are left implicit.

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?

Schema description coverage is 0%, so the lone parameter relies on the description, which only says it is an ID identifying a skill. That confirms the identifier's meaning but gives no format, source, or how to obtain a valid skill ID. Adequate, not compensating for the coverage gap.

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?

"Get a skill by ID" states a specific verb and resource, and "including its full instruction body" distinguishes this detail fetch from a list-style read. It does not name a sibling explicitly, but against create_skill/update_skill/delete_skill the intent is unambiguous.

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?

"Use when reviewing or editing a skill before attaching it to an agent" gives a concrete usage context and implies the read-before-mutate pattern. It stops short of stating exclusions (e.g. when to prefer a list/search tool or update_skill directly), so it is clear context without explicit when-not guidance.

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