Skip to main content
Glama

create_bond

Create a continuity bond (premium 0.1% of posted collateral per 30-day period; first bond's first period waived once per operator account and payer wallet); coverage may not exceed collateral

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": {
      "agent_id": "<agent_id>",
      "beneficiary": "<beneficiary>",
      "collateral_cents": "<collateral_cents>",
      "coverage_cents": "<coverage_cents>",
      "ttl_seconds": "<ttl_seconds>",
      "grace_seconds": "<grace_seconds>"
    },
    "name": "create_bond"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes
beneficiaryYes
ttl_secondsYes
grace_secondsYes
coverage_centsYes
collateral_centsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With zero annotations the description carries the full burden, and it does disclose genuinely useful economics: the 0.1%/30-day premium, the one-time first-period waiver scoped to operator account AND payer wallet, and the coverage<=collateral rule. But it omits whether funds are moved immediately, authorization requirements, idempotency/duplicate behavior, and what happens when ttl or grace elapse — significant gaps for a 6-required-param write tool.

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?

One dense sentence that front-loads the action and packs pricing and constraints into a parenthetical. No filler, though the semicolon-chained clauses are slightly hard to parse at a glance.

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?

No output schema, no annotations, and 6 required undocumented parameters. The description should at minimum explain ttl/grace semantics and what is returned (bond identifier? standing record?), since nothing else in the definition supplies them.

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 description coverage is 0% across 6 required parameters. The description clarifies the relationship between collateral_cents and coverage_cents, which is valuable, but leaves agent_id, beneficiary, ttl_seconds and grace_seconds entirely undefined in both schema and prose — half the parameters have no semantics anywhere.

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?

Specific verb+resource: 'Create a continuity bond', plus the economic mechanics that define what a bond is. It doesn't explicitly contrast with siblings (bond_standing, evaluate_bond), but those are clearly different operations, so confusion risk is low.

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?

No statement of when to create a bond versus using bond_standing/evaluate_bond, no prerequisites (does agent_id need to be registered? must the payer wallet exist?), and no mention of what to do if the coverage-exceeds-collateral validation fails. The only usage-adjacent content is a hard constraint, not guidance.

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.

Resources