Skip to main content
Glama

ArcHive

arc_enclaves

Lists the enclaves (the hive): operator, product, TCB, active or not at the head block, validity window in blocks, registered X25519 key. Read from the ArcHive API index; if the list is briefly unavailable, the tool says so (never a partial list).

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

Input Schema

NameRequiredDescriptionDefault
onlyActiveNotrue = only the active enclaves

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 behavioral burden and does well: it discloses the backing source (ArcHive API index) and a concrete failure contract — if the list is briefly unavailable the tool reports that rather than returning a partial list. It stops short of permissions, rate limits, or freshness/head-block timing beyond the validity window.

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?

Two compact sentences that front-load the resource and its returned fields, then the data source and failure behavior. Dense but purposeful, with no filler.

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 one-parameter, read-only list tool with no output schema, the description is nearly sufficient: it enumerates the returned fields and states the failure mode. Only the relationship to arc_enclave_status and any freshness caveats are missing.

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 coverage is 100%, so the single onlyActive parameter is already documented in the schema. The description's phrase 'active or not at the head block' adds useful framing about what 'active' means, but it does not explain the parameter's true/false semantics beyond what the schema already states.

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 ('Lists the enclaves') and enumerates the fields returned (operator, product, TCB, active status, validity window, X25519 key). It is clear what the tool does, though it never names or contrasts itself with sibling tools such as arc_enclave_status, leaving that differentiation to inference.

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 explicit when-to-use guidance, no prerequisites, and no named alternative for retrieving a single enclave's status (e.g., arc_enclave_status). Usage is only implied by the word 'Lists' and the onlyActive parameter.

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.