Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_log

Read-only

Retrieve a computer's recent terminal history and unattended error log, including printError messages with IDs; filter to new errors or skip terminal text.

Instructions

Show the computer's terminal history and unattended-error log.

lines of recent terminal text (lines marked ! were red), plus every printError message with an id. This is how errors from programs started by hand (or by other code), not through these tools, show up. Pass since_error=<last_error_id from the previous call> to see only new errors; errors_only=True skips the terminal text.

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_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNo
computerNo
errors_onlyNo
since_errorNo

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?

Annotations (readOnlyHint=true, openWorldHint=true) already cover the safety profile and the description is consistent with them. Beyond that it discloses real behavior: error entries carry ids, '!' marks lines that were red, since_error=<last_error_id> returns only new errors, and errors_only suppresses terminal text. It does not describe how the `computer` target is chosen or what happens if no computer is specified, leaving a modest gap.

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, front-loaded with the core purpose before the detail about ids and filtering flags. Every sentence adds information; the only minor awkwardness is the compressed phrase '`lines` of recent terminal text', which reads like parameter syntax embedded mid-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?

For a four-parameter read tool with an output schema (so return shape needn't be explained), the description covers purpose, error provenance, and the two filtering behaviors that matter. The unexplained `computer` parameter is the one real omission, and the openWorldHint implications of querying a remote machine are only implied.

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 explains errors_only and since_error well (including the chaining convention) and implies `lines` controls how much recent terminal text is returned, but the `computer` parameter is never mentioned, leaving one of four parameters undocumented anywhere.

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 specific verb and resource: 'Show the computer's terminal history and unattended-error log.' It further scopes the content ('lines of recent terminal text ... plus every printError message with an id') and explicitly distinguishes itself from the exec/shell siblings by noting it surfaces errors 'not through these tools'.

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 clear usage context: this is how errors from programs started by hand or by other code show up, which tells the agent when this tool is the right one versus the exec/shell tools. It also documents two invocation patterns (since_error chaining for incremental polling, errors_only to skip terminal text). It stops short of explicitly naming an alternative tool for the tool-launched case, so it is clear context without full when-not guidance.

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