Skip to main content
Glama

read_skill

Retrieve a skill by slug to access its full instructions and list of extra files, so agents can load the exact guidance and resources they need.

Instructions

Read one skill by slug: its full instructions and the list of extra files.

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": {
      "slug": "<slug>"
    },
    "name": "read_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose the return payload (full instructions plus extra-file list), which is real value, but says nothing about behavior on a missing or malformed slug, whether the pattern-constrained id is case-sensitive, or whether inline file contents are ever included.

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?

A single tight sentence with the action and result front-loaded and no filler. It is close to the minimum viable length, though the return-value clause could be split for scannability.

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?

For a single-parameter read tool with no output schema, the description covers the essentials: the key and the shape of the response. It leaves out failure behavior and the handoff to read_skill_file for the listed files, which is the natural next step an agent would need.

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?

One parameter at 0% schema description coverage, so the description must compensate. 'By slug' does identify the parameter as the skill's unique key and the schema pattern reveals the allowed format, but there is no guidance on where an agent obtains a valid slug (e.g., from search_tools or search_context).

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?

Specific verb plus resource: 'Read one skill by slug' names the lookup key, and the second clause states exactly what comes back, instructions and an extra-file list. It also implicitly separates itself from read_skill_file by returning the file list rather than file contents, though it never names that sibling.

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?

Usage is only implied: the phrase 'one skill by slug' signals a lookup-by-identifier tool, and mentioning the list of extra files hints that file contents live elsewhere. There is no explicit statement of when to prefer this over read_skill_file or what to do if the slug is unknown.

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