Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_network

Read-only

Lists every peripheral visible to a ComputerCraft computer—direct, wired-modem, or Sable ship bridge—grouped by type with modem, ship, and mass details; also adds method names for peripheral calls.

Instructions

Inventory every peripheral the computer can see (directly attached, on wired-modem networks, and the Create Avionics / Sable ship_* bridge), grouped by type, plus modem info and whether the computer is on a Sable ship (and its mass). methods=True also lists each group's method names once.

Names in the output are exactly what to pass to cc_call / cc_batch / peripheral.call. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
methodsNo
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 'Read-only' is redundant. The description does add real context beyond annotations: grouping by peripheral type, modem info inclusion, the Sable-ship/mass check, and the methods=True side effect of listing method names once. It says nothing about cost, failure modes, or what happens when no peripherals are found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, but the first sentence is long, parenthetical-heavy, and mixes scope enumeration with an unrelated subsystem name. The final line about output names is valuable but sits after the read-only aside rather than being integrated.

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 the description need not detail return values, yet it still describes output shape, which is fine. The gap is the undocumented `computer` parameter and the lack of any guidance on relationship to sibling inventory tools, which matters given a 15-tool family.

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 both parameters, so the description must carry the burden. It explains methods=True reasonably well ('also lists each group's method names once'), but the `computer` parameter is never mentioned at all, leaving half the input surface undocumented.

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 ('Inventory every peripheral the computer can see'), lists the scopes covered (direct, wired-modem networks, Sable ship_* bridge), and notes the output feeds cc_call/cc_batch. It stops short of explicitly distinguishing itself from the sibling cc_peripherals, which an agent must infer from the name alone.

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?

The closing note that output names are 'exactly what to pass to cc_call / cc_batch / peripheral.call' gives a downstream-use hint, and 'Read-only' signals a safe probe. However, there is no explicit statement of when to prefer this over cc_peripherals or cc_computers, and no exclusions or prerequisites.

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