Skip to main content
Glama

list_cells

Lists every locked calculation cell on this machine with what it computes and its required inputs. Use it to discover available verified cells when unsure what exists.

Instructions

List every locked cell on this machine with what it computes and its required inputs. Cheap; use it when unsure what exists.

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": "list_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real value: it discloses that the listing is unfiltered ('every ... on this machine'), the cost profile ('Cheap'), and the shape of each entry. It does not state whether results are paginated or whether any permissions are required to enumerate the machine, which keeps it short of a 5.

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?

Two short sentences, front-loaded with what is returned and followed by the usage cue and cost note. Every clause earns its place with no redundancy.

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 simple, parameterless listing tool with no output schema, the description covers scope, return content, and cost. The only meaningful gap is the absence of any note about result size or pagination when enumerating 'every' cell on the machine.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-argument tool applies. The text adds relevant framing about the scope of the sweep rather than inventing parameter detail.

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 every locked cell') plus the scope ('on this machine') and the return content ('what it computes and its required inputs'). It does not explicitly name a sibling, so an agent must infer the distinction from the discovery framing rather than a direct contrast with find_cell or request_cell.

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?

'Use it when unsure what exists' gives a clear condition for selecting this tool, essentially positioning it as the exploratory/discovery entry point. It lacks an explicit when-not or a named alternative, so the routing guidance is contextual rather than fully enumerated.

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

Deploy Server

Other Tools