Skip to main content
Glama

BondTerminal

Report a gap

bondterminal_report_gap
Idempotent

Report a gap in BondTerminal when you could not complete the user's request: a needed tool or field is missing, a result looks wrong, or a tool description was unclear. Call it at most once per distinct problem per conversation. Do not call it for searches you can fix by retrying or by using bondterminal_search_bonds. Do not include personal data about the user. For a missing bond, use bondterminal_request_bond instead.

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": {
      "category": "<category>",
      "message": "<message>"
    },
    "name": "bondterminal_report_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoWhat the user wanted to do.
toolNoThe BondTerminal tool involved, if any.
messageYesWhat happened, written so a person without this conversation understands it.
categoryYesmissing_capability, wrong_result, unclear_tool, tool_error or other.
severityNoblocked: the user could not go on; workaround: they got there another way; minor: small issue.
identifiersNoISINs, CUSIPs, tickers or descriptions you tried.

Output Schema

NameRequiredDescriptionDefault
statusYes
duplicateNo
report_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"missing_capability, wrong_result, unclear_tool, tool_error or other."
    • addedInput schema / properties / severity / description
      Added value: +"blocked: the user could not go on; workaround: they got there another way; minor: small issue."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description is consistent with those and adds behavior they don't convey — the per-conversation deduplication rule and the PII exclusion. It stops short of saying where the report goes, who sees it, or what happens after submission, which would be the remaining useful disclosure for a 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.

Conciseness5/5

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

Four sentences, each doing distinct work: what it is, the cadence cap, the retry/search exclusion, and the PII plus sibling-alternative rules. Scoping and eligibility are front-loaded before the exclusions.

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

Completeness5/5

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

With an output schema present, annotations covering the safety profile, and full schema description coverage on six parameters, the description supplies exactly the missing layer: eligibility, throttling and content rules. An agent has everything needed to decide and call correctly.

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

Parameters3/5

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

Schema coverage is 100% with documented enums for tool, category and severity, so the schema carries the parameter burden. The description mentions the failure modes that map to categories but adds no field-level syntax, formatting or example content beyond what the schema already states.

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?

Specific verb and resource ('Report a gap in BondTerminal') followed by the exact failure conditions that qualify: missing tool/field, wrong result, unclear description. It also names the sibling it is not (bondterminal_request_bond for missing bonds), so an agent can route without opening schemas.

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?

Gives when-to-use (three qualifying conditions), when-not-to-use (searches fixable by retry or via bondterminal_search_bonds), a frequency cap (once per distinct problem per conversation), a content restriction (no personal data), and an explicit alternative (bondterminal_request_bond for a missing bond). Nothing is left to inference.

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