Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_push

Upload a local UTF-8 text file to a ComputerCraft computer with automatic chunking; overwrite by default or append, so you can deploy programs instead of pasting source.

Instructions

Upload a local UTF-8 text file to the computer, chunked automatically; overwrites unless append=True. Relative local paths are taken from the first folder in CC_MCP_FILES_ROOT; only the folders listed there are allowed. Use this to deploy programs instead of pasting their source through cc_write.

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

Input Schema

NameRequiredDescriptionDefault
appendNo
computerNo
local_pathYes
remote_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: automatic chunking, overwrite-unless-append semantics, UTF-8-only input, and a sandboxed path policy where relative paths resolve against the first entry of CC_MCP_FILES_ROOT and only those folders are writable. What's missing is failure behavior (partial uploads, missing remote directories, size limits) and whether a target computer must be specified.

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?

Three short sentences, each earning its place: capability first, then the overwrite/path constraints, then the sibling-based usage rule. Front-loaded and free of filler.

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?

An output schema exists so return values need no explanation, and the sandbox/encoding rules are covered. However, for a 4-parameter write tool with zero schema coverage, the undefined computer and remote_path semantics leave an agent guessing about multi-machine targeting and remote path legality.

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 must carry the parameter burden. It clarifies append (overwrite default) and local_path resolution rules, but says nothing about remote_path (server-side resolution, whether directories are created, overwrite granularity) or the computer parameter (what null means).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource ('Upload a local UTF-8 text file to the computer') plus key mechanisms (automatic chunking, overwrite vs append), and distinguishes itself from the sibling cc_write by naming it and the use case that selects this tool.

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

Usage Guidelines4/5

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

Gives explicit positive guidance: use this to deploy programs rather than pasting source via cc_write. Also states the default overwrite behavior and how to opt out with append=True. It does not mention the reverse-direction sibling (e.g. cc_pull) or any when-not conditions such as binary files or size limits.

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