Skip to main content
Glama

ArcHive

arc_operator_prepare_register

Enclave registration: anchor block, reading the VM's /attest (if enclaveUrl and operator are given), encoded registerEnclave transaction. PREPARES only: signs and sends nothing, returns the data the user signs in their wallet.

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": {
      "productId": "<productId>"
    },
    "name": "arc_operator_prepare_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
operatorNo
productIdYes
enclaveUrlNo
includeCalldataNofull calldata (default: yes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 well on the critical trait: "PREPARES only: signs and sends nothing, returns the data the user signs in their wallet." That discloses the non-mutating contract and the hand-off to the wallet, which an agent needs to avoid double-signing or assuming the transaction is submitted. It stops short of stating auth/permission requirements or what happens when enclaveUrl is supplied without operator.

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 with the action and the critical prepare-only caveat front-loaded. The telegraphic phrasing ("anchor block", "encoded registerEnclave transaction") is dense but each clause adds information; nothing is redundant.

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 four-parameter preparation tool with no annotations and no output schema, the description covers the core contract (no signing/sending, returns signable data) and one conditional behavior. It leaves the required productId's role, the calldata default, and any failure modes unexplained, so it is adequate but not complete.

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 description coverage is only 25% (only includeCalldata is annotated), so the description must compensate. It does partially: it explains that enclaveUrl and operator must both be present to trigger the /attest read, which is meaningful semantics the schema lacks. productId, the lone required parameter, and includeCalldata receive no explanation in the description.

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 names a specific action and resource: it prepares an "encoded registerEnclave transaction" for enclave registration, and mentions the supporting steps (anchor block, reading /attest). An agent can tell this is the registration counterpart to prepare tools like arc_operator_prepare_bond, though the description never names that sibling 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 rather than stated: you call this to register an enclave, and the conditional clause "reading the VM's /attest (if enclaveUrl and operator are given)" tells the agent when the attestation path is taken. There is no explicit when-not guidance or routing to alternative tools such as arc_enclave_status or arc_enclaves.

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.