Skip to main content
Glama

ArcHive

arc_operator_prepare_bond

Operator bond deposit: EIP-3009 authorization for bond(), or encoded approve + bondFrom; checks balance, ban and minimum bond. PREPARES only: signs and sends nothing, returns the data the user signs in their wallet.

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

Input Schema

NameRequiredDescriptionDefault
amountNoamount in USDC
operatorNo
productIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 much of it: 'PREPARES only: signs and sends nothing, returns the data the user signs in their wallet' clearly establishes that nothing is submitted on-chain and the caller must complete the signature themselves. It also discloses that balance, ban and minimum bond are checked. It does not describe what happens when those checks fail or what the return payload looks like.

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 sentences, no filler, with the operational caveat ('PREPARES only') given its own emphasis. The first sentence is dense with protocol jargon, and the most important constraint – that nothing is signed or sent – appears second rather than front-loaded.

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 3-parameter tool with no annotations and no output schema, the definition covers purpose, non-mutating behavior and preconditions, which is the core. It still omits failure behavior, the shape of the returned signing payload, and the chain/network context needed to actually act on the result.

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

Parameters2/5

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

Schema coverage is only 33% – only 'amount' has a description – so the description must compensate for 'operator' and 'productId', and it does not explain either. It mentions two transaction paths (EIP-3009 authorization vs encoded approve + bondFrom) but never says which parameter or condition selects a path, leaving the caller unable to map inputs to behavior.

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 verb and resource ('Operator bond deposit', preparing data for bond()/bondFrom) and states it prepares rather than executes, which distinguishes it in intent from write-side tools. However, the purpose is wrapped in contract-level jargon (EIP-3009, bond(), bondFrom) and never explicitly distinguishes it from siblings like arc_operator_prepare_register or arc_operator_plan.

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 by 'Operator bond deposit' and the note that it checks balance, ban and minimum bond, which tells an agent the preconditions it validates. There is no explicit when-to-use vs alternative guidance, no statement that this must precede a separate registration/execution step, and no exclusions.

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.