Skip to main content
Glama

Read a file in the server folder

read_file
Read-onlyIdempotent

Retrieve contents of files inside the Minecraft test server folder, including configs, datapack files, and logs; use base64 encoding for binary files.

Instructions

Reads a file inside the test server folder: configs, datapack files, logs. Use encoding base64 for binary files. The RCON password in server.properties is hidden. Limited to maxFileBytes.

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
pathYesPath inside the test server folder, for example "world/datapacks/my_pack/pack.mcmeta"
encodingNotext

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/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), and the description adds real value beyond them: the RCON password in server.properties is redacted, and output is bounded by maxFileBytes. It does not say whether exceeding maxFileBytes errors or truncates, nor what the response looks like, which are the remaining behavioral gaps.

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?

Four short sentences, front-loaded with what the tool does, then the binary-file rule, then the two caveats (secret redaction, size limit). Nothing is repeated and nothing is padding.

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 two-parameter read tool this is close to sufficient, and annotations carry the safety profile. With no output schema, however, the description leaves the return shape unstated (string content vs base64 payload) and does not define the failure mode when a file is missing or over maxFileBytes.

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 50%: path is documented in the schema, encoding has an enum and default but no prose. The description compensates for encoding by explaining that base64 is for binary files, and reinforces the path constraint ('inside the test server folder'), so it does add meaning beyond the schema — but only marginally, and it never explains the text/default case.

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 and resource (reads a file) and scopes it to the test server folder, with concrete examples of file kinds (configs, datapack files, logs). It does not explicitly distinguish itself from siblings like list_files or server_logs, and naming 'logs' as a target slightly overlaps with server_logs, but the core purpose is unambiguous.

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

Usage Guidelines3/5

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

It gives one actionable usage rule — use encoding base64 for binary files — which is genuinely helpful. However, it offers no guidance on when to reach for this tool versus list_files (discovery) or server_logs (log retrieval), so the agent must infer selection from names alone.

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