Skip to main content
Glama

evaluate_bond

Evaluate a bond: dual-condition payout (ledger deadline AND 2-of-3 witness quorum), UNRESOLVED fail-closed

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": {
      "bond_id": "<bond_id>"
    },
    "name": "evaluate_bond"
  }
}

Input Schema

NameRequiredDescriptionDefault
bond_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the dual-condition logic and fail-closed UNRESOLVED behavior, which is useful, but it omits critical traits: whether invoking it triggers a payout or is read-only, side effects, idempotency, permissions, and failure behavior beyond the unresolved state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler, which is efficient. However, the compressed jargon ('UNRESOLVED fail-closed') reduces readability and could have been expressed more clearly without much added length.

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 financial/payout-oriented operation with no annotations and no output schema, the description is materially incomplete. It explains the conditions but not what evaluation returns, whether state changes, or how callers should interpret success versus fail-closed outcomes.

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%, and the description says nothing about bond_id semantics, format, or lookup expectations. While a single identifier parameter is largely self-explanatory, the description adds no meaning beyond the schema and does not compensate for the lack of documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ('Evaluate a bond') and adds the payout condition, which helps distinguish it from a pure status read. However, 'evaluate' is ambiguous: it does not clarify whether this checks eligibility, executes a payout, or mutates bond state, and it does not explicitly contrast with siblings like bond_standing.

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?

There is no explicit when-to-use guidance, no prerequisites, and no alternatives named. The agent is left to infer whether to call this instead of bond_standing or witness_status, and when evaluation should happen.

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