Skip to main content
Glama

read_skill_file

Reads an additional file from a skill by slug and path so agents can retrieve supporting content when needed.

Instructions

Read one extra file of a skill by its path.

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>",
      "path": "<path>"
    },
    "name": "read_skill_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It implies a read-only operation but says nothing about failure modes for a missing path, path traversal or sandbox restrictions, size or encoding of returned content, or whether the path is relative to the skill directory.

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 short sentence with the distinguishing qualifier ('extra file') front-loaded and no filler. It is efficient, though the brevity contributes to the gaps noted elsewhere.

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?

For a two-parameter tool with no annotations, no output schema, and no parameter documentation, the description is too thin. An agent cannot tell how the slug and path combine, what path syntax is valid, or what comes back.

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%, with two required parameters left bare. The description gestures at 'path' but adds no format or resolution rules, and the 'slug' parameter is never mentioned at all, leaving the relationship between slug and path unexplained.

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: 'Read one extra file of a skill'. The qualifier 'extra' implicitly sets it apart from read_skill, which likely returns the skill itself. It stops short of naming that sibling or defining what counts as an 'extra file'.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisite (for example, must the skill be read first?), and no mention of read_skill as the alternative for the skill body. Usage can only be inferred from the word 'extra'.

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