Skip to main content
Glama

Margrave

read_skill_file

Read one file inside a skill directory. Use a path from the file list that load_skill returns.

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

Input Schema

NameRequiredDescriptionDefault
idYes
pathYes
revisionNo

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 behavioral burden. 'Read' plus 'one file' discloses that this is a non-mutating, single-file operation, which is the key fact. It says nothing about failure behavior for an invalid or directory path, size limits, or whether content is truncated, which matters for a tool reading arbitrary skill files.

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, both load-bearing, with the core purpose front-loaded and the sourcing constraint immediately after. Nothing is padded or restated from the title.

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?

There are no annotations and no output schema, so the description must convey both behavior and parameter meaning, and it leaves the 'id' and 'revision' parameters undefined. An agent cannot tell what revision selects or whether omitting it means latest. Adequate on purpose, insufficient on the parameter surface.

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 three parameters, so the description must compensate and largely does not. It clarifies only 'path' (source it from load_skill's file list), leaving 'id' — which skill the directory belongs to — and the optional 'revision' completely unexplained. Two of three parameters carry no semantics anywhere.

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 specific verb ('Read') and a precise resource ('one file inside a skill directory'), with the singular 'one file' making the scope explicit. It also implicitly separates itself from load_skill, which is described as returning the list rather than file contents. It stops short of a crisp one-line differentiation from find_skills, but an agent can tell what it fetches.

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 real prerequisite: use a path taken from the file list that load_skill returns, which establishes the correct call sequence with a sibling tool. There is no explicit 'do not use this for X' or guidance on when load_skill or find_skills is preferable, so it is context-rich but lacks exclusions.

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