Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_call

Calls a ComputerCraft peripheral method with JSON arguments and returns its results or error data, so you can inspect or control in-game peripherals.

Instructions

Call one peripheral method and return its result(s): peripheral.call(name, method, *args).

args is a JSON list (numbers, strings, booleans; objects/arrays become Lua tables). Errors from the peripheral (wrong argument, bad enum value) come back as data. Getters are safe; setters, assemble/disassemble and similar change the live world - ask first. Setters wait for the next game tick (game must be focused).

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": {
      "peripheral": "<peripheral>",
      "method": "<method>"
    },
    "name": "cc_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
methodYes
timeoutNo
computerNo
peripheralYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No description of the tool contradicts the annotations. The description adds real context beyond the annotations: peripheral errors return as data rather than throwing, and setters block until the next game tick with the game focused. That said, the description does not cover the 30s default timeout or how an error result is shaped, which matters for a mutating, open-world call.

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?

Four tight sentences, front-loaded with the signature and then the arg encoding, error behavior and safety caveats in order of importance. Dense but no filler; minor cost is that the safety caveat is buried in the third sentence.

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

Completeness4/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 no explanation, and the description covers the highest-risk semantics (tick-blocking setters, game focus requirement, errors-as-data). The remaining gap is the undocumented `timeout` and `computer` parameters, which an agent cannot infer from a 0%-coverage schema.

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 0%, so the description must carry the parameter load. It explains `args` well (JSON list; primitives, with objects/arrays coerced to Lua tables) and implies `peripheral`/`method`, but `timeout` and `computer` are never mentioned, leaving two of five parameters undocumented anywhere.

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 opens with a specific verb and resource: 'Call one peripheral method and return its result(s)', and even shows the underlying call signature `peripheral.call(name, method, *args)`. An agent can tell this invokes a peripheral method rather than executing arbitrary code (cc_exec) 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?

It gives a useful safety rule: getters are safe, while 'setters, assemble/disassemble and similar change the live world - ask first'. That is genuine when-to-be-careful guidance, but there is no explicit routing to alternatives like cc_exec or cc_batch, so the agent must infer which tool to pick.

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