Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_peripherals

Read-only

List attached peripherals and their types, optionally including each one's method names, to inspect what a ComputerCraft computer can control.

Instructions

List attached peripherals (name and type); methods=True also lists each one's method names.

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

Input Schema

NameRequiredDescriptionDefault
methodsNo
computerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safety and reach are covered. The description adds the useful detail that the response contains peripheral name/type and, with methods=True, per-peripheral method names. It says nothing about scoping (which host is queried) or result size, which matters for an open-world read.

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?

A single compact sentence that front-loads the primary behavior and appends the flag semantics, with no filler. Slightly dense punctuation (semicolon plus parenthetical) rather than wasteful.

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 methods flag is well covered. However, for a two-parameter open-world tool, the unscoped computer parameter and the absence of any selection guidance leave real gaps for an agent deciding how to call it.

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 parameter meaning. It fully explains the non-obvious boolean (methods=True adds each peripheral's method names), but the second parameter, computer, is never mentioned, leaving its default/null behavior 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?

The description names a specific verb and resource ("List attached peripherals") and states the returned fields (name and type), so an agent knows exactly what the tool produces. It does not explicitly distinguish itself from look-alike siblings such as cc_computers or cc_list, which keeps it 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?

There is no when-to-use or when-not-to-use guidance and no routing to an alternative tool. The only usage signal is the conditional behavior of the methods flag, which describes output detail rather than tool selection.

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