Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_pull

Download a remote file (text, CSV, or log) to a local folder, automatically paging large files and overwriting the local copy; only allowed CC_MCP_FILES_ROOT folders are accessible.

Instructions

Download a computer file (text/CSV/log; large files are paged automatically) into a local folder. Overwrites the local file. Only the folders listed in CC_MCP_FILES_ROOT are allowed.

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": {
      "remote_path": "<remote_path>",
      "local_path": "<local_path>"
    },
    "name": "cc_pull"
  }
}

Input Schema

NameRequiredDescriptionDefault
computerNo
local_pathYes
remote_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations cover readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description adds genuinely non-structured context: overwrite semantics, automatic paging for large files, and the CC_MCP_FILES_ROOT path restriction (a real auth/sandbox constraint). The only soft tension is 'overwrites the local file' against destructiveHint=false, though that annotation conventionally refers to remote state, so this is not a contradiction.

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?

Three short sentences, verb and resource front-loaded, with the safety constraint last. The paging behavior is somewhat buried in a parenthetical, but nothing is wasted.

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?

The output schema exists, so return values need not be explained, and the sandbox/overwrite behavior is covered. However, with a 0%-documented three-parameter schema and no explanation of the 'computer' selector or path conventions, an agent still has gaps to fill before calling correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three parameters, so the description must carry the load, yet it never explains remote_path versus local_path formats or what the optional 'computer' selector does or how it defaults. The content-type hint ('text/CSV/log') only loosely gestures at what remote_path may point to.

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 ('Download a computer file') plus the destination ('into a local folder'), which implicitly contrasts with the upload-oriented sibling cc_push. An agent can tell what it does without opening the schema, though no sibling is named 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?

Usage is implied by the direction (pull from remote computer to local folder), but there is no explicit when-to-use versus when-not guidance and no named alternative such as cc_push or cc_read. The one hard rule given is a constraint, not a selection guideline.

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