Skip to main content
Glama
Sign In
MCP DevOps Kit

MCP DevOps Kit

by Jmfrodero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

fs_read

Read file contents from a given path, with an optional maximum number of lines.

Instructions

Read file contents

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

Input Schema

NameRequiredDescriptionDefault
pathYesFile path to read
max_linesNoMaximum number of lines to read (default: 1000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral traits. It only states what it does (read file contents) but does not disclose any limitations (e.g., text vs binary, encoding, file size limits) or side effects (none expected).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one short sentence), which is efficient but borderline under-specified. It front-loads the purpose but lacks detail that could be added without verbosity.

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?

Given the tool has two parameters, no output schema, and no annotations, the description is too minimal. It does not explain what the tool returns (e.g., file content as string) or how max_lines affects behavior. A more complete description would clarify return format and default behavior.

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?

The input schema covers both parameters with descriptions (path and max_lines). The description does not add any additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 'Read file contents' clearly identifies the verb (Read) and resource (file contents), but it does not explicitly distinguish itself from siblings like fs_ls or fs_stats. However, given the simplicity of the tool and the family, the purpose is clear enough.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., fs_ls for directory listing, docker_logs for container logs). No exclusions or context hints are given.

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

Deploy Server

Other Tools