Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_list

Read-only

Lists files and folders in a specified computer directory, returning names, directory status, and sizes so you can inspect available content before reading or running programs.

Instructions

List a directory on the computer (names, whether each is a directory, sizes).

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

Input Schema

NameRequiredDescriptionDefault
pathNo
computerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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. The description adds only the returned field list, which the existing output schema already provides, and says nothing about permission requirements, behavior on a nonexistent path, or how the default empty path is resolved.

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 front-loaded sentence with no filler and the core action stated first. The parenthetical return-field list is slightly redundant given the output schema, keeping it just short of a 5.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, and the output schema relieves the description of explaining return values. But with zero schema description coverage, the description should have clarified the two parameters, especially how `computer` is chosen among the many cc_computers-related siblings, and it does not.

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 two parameters, and the description does not compensate: it never explains the expected path format (absolute vs. relative) or what the empty-string default means. The single word "computer" gestures at the second parameter but gives no clue about its semantics when null or which computer is implied.

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 ("List a directory on the computer") and even names the returned fields (names, is-directory flag, sizes), so an agent knows exactly what it gets. It does not, however, distinguish itself from neighbors like cc_read or cc_pull, which also touch the filesystem.

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 guidance, no exclusion of alternatives (e.g., use cc_read for file contents rather than directory listings), and no prerequisites such as whether the path must exist or be readable. The agent must infer the intended context from the tool name alone.

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