Skip to main content
Glama

bond_standing

Bond standing query ($0.001): state, collateral, premium, paid_cents — never the agent secret

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": "bond_standing"
  }
}

Input Schema

NameRequiredDescriptionDefault
bond_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds useful behavioral context by disclosing a cost ($0.001) and a privacy boundary ('never the agent secret'), but it does not state read-only behavior explicitly, permissions, error conditions, or side effects.

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 a single compact sentence with the core purpose front-loaded. The cost and privacy constraint are useful, though the terse field list and em-dash phrasing are slightly cryptic.

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?

There is no output schema, so the description appropriately lists returned fields. However, it leaves the sole required parameter unexplained and does not clarify prerequisites or how this query relates to sibling tools.

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?

The input schema has 0% description coverage and only one parameter, bond_id, which the description does not explain at all. The parameter name is inferable from context, but format, constraints, and meaning are undocumented in both schema and 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 states a clear verb and resource: a bond standing query, and it names the specific fields returned (state, collateral, premium, paid_cents). This is clear enough to distinguish it from create_bond, but it does not explicitly differentiate it from evaluate_bond or witness_status.

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 guidance on when to use this tool versus alternatives such as evaluate_bond or witness_status. It is implied that the tool retrieves bond standing, but the description gives no explicit context, exclusions, or routing 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