Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_read

Read-only

Read files from a ComputerCraft computer inside Minecraft, up to about 60 KB per call. Use the offset parameter to page through larger files when more content remains.

Instructions

Read a file from the computer (up to ~60 KB per call; page with offset when told more remains).

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

Input Schema

NameRequiredDescriptionDefault
pathYes
offsetNo
computerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description usefully adds the ~60 KB per-call cap plus a pagination signal. It says nothing about error behavior for missing paths, permissions, binary/encoding handling, or what the "more remains" signal looks like in the response.

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?

A single tight sentence with the resource and size limit front-loaded and the pagination hint in a parenthetical. No wasted words, though the parenthetical phrasing ("when told more remains") is slightly elliptical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be described, and annotations cover the safety profile. For a three-parameter read tool, the remaining essentials (what it reads, size cap, how to continue) are all stated; only `computer` semantics is a minor gap.

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 0%, so the description carries the burden; it explains offset's purpose (pagination) but only implicitly covers path and never explains the `computer` parameter, which determines the target machine and is non-obvious given the multi-computer tool family.

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 ("Read a file from the computer") and adds the scope constraint of ~60 KB per call. It is clearly distinct from write/exec siblings like cc_write or cc_exec, though it does not name any alternative explicitly.

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?

Gives one concrete operational rule: page with offset when told more remains. It offers no guidance on when to prefer this over siblings such as cc_exec or cc_shell for inspecting file contents, so selection is left to inference.

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