Skip to main content
Glama

Read one spec file

get_spec_file
Read-onlyIdempotent

Returns one file of a spec as text. Use it for a file pull_spec listed without content, unless its note says to download it. A long file comes in parts: when the answer has nextLine, call again with that line.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe spec's id, like username/name.
lineNoThe first line to return. Leave it out to start at the top.
pathYesThe file's path, as pull_spec and get_spec list it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the pagination contract: long files come in parts and a nextLine field in the answer means call again with that line. That is real behavioral disclosure beyond the annotations. It stops short of describing failure modes (bad id or path, missing file), 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?

Three short sentences, front-loaded with what the tool returns, then routing, then pagination. No filler, and the most operationally important detail (the nextLine loop) is stated plainly rather than buried.

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?

With no output schema, the description carries the return-shape burden and does so for the main case: text content plus the nextLine pagination marker. Missing are error/empty-file behavior and whether the note field is surfaced in this response, but nothing an agent needs to make a correct first call is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining how the optional 'line' parameter is actually driven — it is the continuation handle returned as nextLine. That connects the parameter to the response loop in a way the schema text alone does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns one file of a spec as text') and implicitly separates itself from pull_spec (which lists files without content) and get_spec (which lists files). An agent can distinguish the single-file read from the listing siblings without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing: use it for a file pull_spec listed without content, and skip it when the note says to download instead. That names both the selecting condition and the exclusion, which is the strongest form of when-to-use 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