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

Input Schema

NameRequiredDescriptionDefault
idYes
pathYes
revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / revision
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

B3.1/5.0
Behavior2/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, and it says almost nothing beyond "read." It does not state what is returned (raw text, binary, truncated content), whether the operation has side effects, how errors such as a bad path or missing revision are surfaced, or any size/encoding constraints.

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?

Two short sentences, front-loaded with the action and followed by the usage constraint; there is no filler. It is efficient, though the extreme terseness leaves room that a short clause on the `id`/`revision` parameters could have used productively.

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?

With three undocumented parameters, no output schema, and no annotations, the definition is not complete enough for an agent to call it confidently. Nothing explains the skill `id`, when to pass `revision`, or what the response contains.

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%, so the description must compensate for all three parameters. It partially explains `path` by pointing to the list from load_skill, but the required `id` and the optional `revision` are never mentioned, leaving an agent to guess what they refer to and when revision matters.

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?

"Read one file inside a skill directory" gives a specific verb and resource that is clearly distinct from loading a skill or finding skills. The only weakness is that it names the sibling as "load_skill" rather than the actual sibling identifier, so the agent must map the reference itself.

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?

It states a real precondition for use: the path must come from the file list returned by load_skill, which establishes a correct call ordering. It offers no explicit exclusions or guidance about what to do if the file or skill is missing, but the positive usage context is clear.

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