Skip to main content
Glama

ArcHive

arc_enclave_status

State of ONE enclave by its signer: operator, product, TCB, expiry, active or not, the operator's bond (total, available, 24 h exposure on this product).

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": {
      "signer": "<signer>"
    },
    "name": "arc_enclave_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
signerYes0x… address of the enclave's signer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 behavioral burden. It does valuable work by disclosing the shape of the returned state, including the bond breakdown with a 24 h exposure window on the product, but it says nothing about read-only semantics, what happens if the signer is unknown, or any auth/rate constraints.

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 key scoping constraint ('ONE enclave', 'by its signer') front-loaded and no filler. The field enumeration is compact rather than padded.

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?

With one required parameter and no output schema, the description's enumeration of returned fields (operator, product, TCB, expiry, active state, bond totals) does most of the completeness work an agent needs. Only error/not-found behavior and read-safety context 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% for the single 'signer' parameter, and the input schema already documents it as a 0x… address. The description repeats 'by its signer' without adding format, validation, or normalization guidance beyond the schema, so baseline 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?

States a specific resource (the state of ONE enclave) and the lookup key (its signer), and enumerates the fields returned: operator, product, TCB, expiry, active flag, bond figures. The capitalized 'ONE' implicitly separates it from a list-style sibling such as arc_enclaves, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call this when you already know a signer and need that single enclave's status. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. arc_enclaves for enumeration), so the agent must infer the routing.

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.