Skip to main content
Glama

BondTerminal

Request a bond

bondterminal_request_bond
Idempotent

Request that BondTerminal add a bond it does not cover yet. Call only after the user agreed. Use the ISIN from a bondterminal_get_bonds miss.

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": {
      "isin": "<isin>"
    },
    "name": "bondterminal_request_bond"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinYesISIN of the bond to add, with a valid check digit.
noteNoWhy the user needs the bond, in a sentence.

Output Schema

NameRequiredDescriptionDefault
statusYes
requested_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / isin / description
      Added value: +"ISIN of the bond to add, with a valid check digit."
    • addedInput schema / properties / note / description
      Added value: +"Why the user needs the bond, in a sentence."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description adds the valuable behavioral constraint that this must follow explicit user consent rather than firing autonomously. It does not say what happens after the request (review, delay, acknowledgement), which is the only real gap.

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

Conciseness5/5

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

Three short sentences, the purpose front-loaded and the usage constraint immediately after. Nothing is repeated from the title or schema and no sentence is filler.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the annotations plus idempotent hint cover the side-effect profile. For a two-parameter request tool this is nearly complete, lacking only a note on what the request triggers or how it is confirmed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by stating the provenance of the isin argument (a get_bonds miss), which is real guidance the schema does not give. The optional note parameter is not mentioned, so it is not fully additive.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Request that BondTerminal add') and resource ('a bond it does not cover yet'), so the agent immediately knows this is a coverage-request action, not a lookup. It also implicitly distinguishes itself from bondterminal_get_bonds by framing this as the fallback for a miss.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit precondition ('Call only after the user agreed') and names the triggering scenario and sibling ('Use the ISIN from a bondterminal_get_bonds miss'). An agent knows exactly when to reach for this tool and where the input comes from.

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