Skip to main content
Glama

ArcHive

arc_machines_list

An operator's machines (nodes) from the ArcHive API: mode (tdx, dstack, demo), online, last heartbeat, product, enclave URL and signer, diagnostics OK, registered. Read only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operator": "<operator>"
    },
    "name": "arc_machines_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
operatorYes0x… address of the operator

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that the operation is read-only and lists the returned fields (mode, online, last heartbeat, product, enclave URL/signer, diagnostics OK, registered), which effectively substitutes for the absent output schema. It does not cover ordering, pagination, behavior for unknown/unregistered operators, or whether all machines or only online ones are returned.

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 dense sentence with the resource stated first and the returned fields listed after, with no filler. The field enumeration is telegraphic but every element earns its place.

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?

For a simple read-only list tool with one fully documented parameter, the description covers resource, safety, and return fields adequately. It stops short of what an agent would want when the result is empty or ambiguous, such as ordering, filtering, and whether the operator must be registered.

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?

There is a single parameter with 100% schema description coverage, and the schema already documents it as a '0x… address of the operator'. The description's 'An operator's machines' adds only light framing and no format, validation, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 identifies a specific resource (an operator's machines/nodes) and scope (scoped to one operator address) from the ArcHive API, and enumerates the fields returned so the agent knows what data comes back. It is not verb-led and does not explicitly distinguish itself from siblings such as arc_enclaves or arc_machine_diagnostics, but the resource is unambiguous.

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 guidance on when to use this versus alternatives; the sibling list contains arc_enclaves and arc_machine_diagnostics, which plausibly overlap, yet the description offers no routing criteria. The only usage-adjacent statement is 'Read only', which is a safety property rather than a when-to-use rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.