Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

read-file

Read contents from a local file using an absolute or relative path.

Instructions

Read contents of a file from the local filesystem

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": {
      "path": "<path>"
    },
    "name": "read-file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute or relative path to the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/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 does not meet it. It implies a read-only operation but says nothing about encoding, binary files, large-file limits, error behavior for missing paths, or whether the whole file is returned.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than polished structure.

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 simple one-parameter read tool with no output schema, the definition covers the essentials needed to make a call. It leaves meaningful gaps around file types, encoding, and failure modes that an agent would want before invoking it on arbitrary paths.

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 coverage is 100% with a single documented 'path' parameter, so the schema already explains that absolute or relative paths are accepted. The description adds no further meaning about path resolution, working directory, or symlink behavior, which is the baseline-3 outcome for a fully documented single parameter.

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 resource ('contents of a file') with an explicit location scope ('local filesystem'). It is clear on its own, but it never distinguishes itself from the sibling read-pdf, leaving an agent to guess whether PDFs should go here or there.

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 or when-not-to-use guidance, no mention of alternatives such as read-pdf, and no prerequisites. The only implied usage is 'you have a file path and want its contents,' which the agent must infer.

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