Skip to main content
Glama

BondTerminal

API usage

bondterminal_get_usage
Read-onlyIdempotent

Return the authenticated plan, calculation/read usage, remaining quotas, and reset time. YTM conventions are percent, spreads are basis points, and bond prices are per 100 face; this tool returns no bond data and has no batch input. Billing: free; consumes no calculation or read units.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bondterminal_get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planYes
readsYes
resetsAtYes
calculationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious context: that the call is free and consumes no calculation or read units, and that there is no batch input — relevant for an agent budgeting quota across calls.

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 opening sentence is well front-loaded and the billing note earns its place. The middle sentence about YTM/spread/price conventions is largely wasted, since the same sentence concedes the tool returns no bond data — that unit-convention detail belongs on the calculation tools, not here.

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?

Return contents are enumerated and an output schema exists, so return-shape explanation is unnecessary. Billing and no-batch constraints are covered. Only minor gap is no mention of authentication requirements beyond the phrase 'authenticated plan'.

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?

Zero parameters, which is the baseline-4 case; the schema also confirms no arguments are accepted. The description reinforces this by noting there is no batch input, removing any temptation to pass a list.

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?

States a specific verb and enumerates the exact resource returned: authenticated plan, calculation/read usage, remaining quotas, and reset time. This is clearly distinguishable from siblings like bondterminal_calculate or bondterminal_get_terms, which deal with bond data rather than account state.

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

Usage Guidelines4/5

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

The description gives clear context for when this applies (checking plan status and quota consumption) and explicitly excludes bond-data lookups, steering the agent away from using it as a data tool. It does not, however, name a specific alternative to use instead for any scenario.

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