Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_ping

Read-only

Checks that a Minecraft ComputerCraft computer responds and returns its ID, label, uptime, game day, and free disk space, confirming the bridge connection works.

Instructions

Check that a computer answers; returns its id, label, uptime (clock), game day and free disk space.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cc_ping"
  }
}

Input Schema

NameRequiredDescriptionDefault
computerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds that the probe returns diagnostic values (clock uptime, game day, free disk), but it omits failure semantics: whether an unreachable computer raises an error, returns a flag, or blocks on a timeout — the key behavioral question for a ping tool.

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?

One compact sentence with the action front-loaded and the return payload appended. No filler, no redundancy.

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?

It has an output schema, so listing return fields in prose is largely redundant and the return contract needs no description. However, with an unexplained nullable 'computer' parameter and no failure/timeout behavior, the definition is only adequate rather than complete for a diagnostic tool.

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 the single 'computer' parameter, and the description never mentions it at all. Critically, the schema default is null and nothing explains what happens then (local/default computer? all computers?), leaving the one parameter's meaning undocumented in both places.

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: 'Check that a computer answers,' which reads clearly as a reachability/health probe, and enumerates what comes back (id, label, uptime, game day, free disk space). It doesn't name any sibling (e.g., cc_computers or cc_exec) to sharpen the boundary, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description offers no explicit when-to-use guidance, no prerequisites, and no exclusions versus siblings like cc_computers or cc_call. Any guidance (e.g., 'use as a pre-flight check before cc_exec') is left entirely to inference.

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