Skip to main content
Glama

Codethrift

Read a file

read_file
Read-onlyIdempotent

The text of one file from an entry (UTF-8, up to 256 KB), at a branch, tag or commit.

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": {
      "repo": "<repo>",
      "path": "<path>"
    },
    "name": "read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoBranch, tag or commit. Defaults to the default branch.
pathYesPath inside the repository, for example scan_health.py.
repoYesRepository as owner/name, for example commons/film-scan-health.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add real behavioral facts (UTF-8 decoding and a 256 KB ceiling on returned text), but it never says what happens at the boundary — truncation or hard failure — which is the one thing an agent most needs before reading a large file.

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?

A single sentence that front-loads the returned value and then qualifies it, with no boilerplate, hedging, or repetition. Every clause carries information the agent can act on.

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 three-parameter read tool with full schema coverage and no output schema, most of what an agent needs is already structured. The gaps are the unspecified behavior at the 256 KB limit and no indication of error cases such as a missing path or bad ref, which the description should carry since no output schema does.

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?

Schema description coverage is 100%, with each of repo, path and ref documented including format examples and a default for ref, so the baseline is 3. The description restates the ref semantics ("branch, tag or commit") without adding syntax or precedence detail beyond the schema, so it does not lift the score.

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 names a specific resource ("the text of one file from an entry") and adds scope qualifiers (encoding, size cap, ref types), so the agent knows this is a single-file content read. It does not differentiate itself from the sibling get_entry, which by name alone sounds related, so an agent could still hesitate between fetching entry metadata and file text.

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 when-to-use guidance, no exclusion conditions, and no mention of alternatives among get_entry, search, or report. Usage can only be inferred from the name "read_file" and the word "entry", which is the definition of implied-at-best rather than stated 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