Skip to main content
Glama

ArcHive

arc_operator_plan

Step-by-step plan to become an operator: Intel TDX VM (Phala), app-compose, /attest, bond, registerEnclave, renewal; the bond rules with the figures read on-chain.

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_operator_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
operatorNo
productIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/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 indicates bond figures are read on-chain, but does not say whether the tool is read-only, whether it executes any listed steps, what permissions are needed, or what the caller receives.

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?

The description is compact and front-loads the core purpose before the colon-separated workflow list. It is dense with protocol jargon, but it does not waste many words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter planning tool with no annotations and no output schema, the definition is thin on parameter usage, return contents, and how it relates to the prepare_* siblings. It communicates the high-level sequence but not enough to invoke or interpret the tool confidently.

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

Parameters1/5

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

Two parameters, operator and productId, have 0% schema description coverage, and the description does not explain either one. 'Operator' appears only as a role in the workflow, and productId is never mentioned, so the description adds no usable parameter meaning.

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 deliverable, a step-by-step plan to become an operator, and enumerates the workflow stages. It does not explicitly distinguish itself from the closest siblings arc_operator_prepare_bond and arc_operator_prepare_register.

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?

It gives no explicit when-to-use or when-not-to-use guidance and does not name the prepare_bond or prepare_register alternatives. At most, 'plan to become an operator' implies this is an overview step, leaving the agent to infer 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.