Skip to main content
Glama
T-Bank Invest MCP Server (read-only)

T-Bank Invest MCP Server (read-only)

by Sicness

list_bonds

Read-only

Fetch the complete bond reference list with every field for scripts and bulk exports; select tradeable or all instrument statuses.

Instructions

Get the full reference list of bonds: every field of every bond.

A dump for scripts, not something to read: about 1,600 bonds and 2.4 MB of JSON with INSTRUMENT_STATUS_BASE — far more than fits in a model's context; a client saves such a result to a file or refuses it. INSTRUMENT_STATUS_ALL is 38 MB, and the API drops the connection before sending it all. To find particular bonds use find_instrument with instrument_kind="bond", and get_bond_by for the details of one.

Args: instrument_status: INSTRUMENT_STATUS_BASE (tradeable) or INSTRUMENT_STATUS_ALL

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

Input Schema

NameRequiredDescriptionDefault
instrument_statusNoINSTRUMENT_STATUS_BASE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations mark this as readOnly and openWorld, but the description adds substantial operational context beyond them: the approximate result size, that it exceeds a model's context, that clients may save it to a file or refuse it, and that INSTRUMENT_STATUS_ALL causes the API to drop the connection. This is exactly the kind of behavioral disclosure annotations cannot provide.

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?

The purpose is front-loaded in sentence one, followed immediately by the critical size/failure warning and then alternatives. Every sentence earns its place by preventing a likely misuse, despite the definition being longer than typical.

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 no output schema and only annotations covering safety, the description explains the return scale, the failure mode of the larger status, and the correct alternative tools. Nothing an agent needs to call this correctly is missing.

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 description coverage is 0%, so the description carries the burden of explaining instrument_status. It does so by defining INSTRUMENT_STATUS_BASE as 'tradeable' and warning that INSTRUMENT_STATUS_ALL is 38 MB and fails, which adds meaning beyond the bare enum values. The default value is only implicit, keeping this just short of 5.

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 states a specific verb+resource: 'Get the full reference list of bonds: every field of every bond.' It also distinguishes this tool from siblings by naming find_instrument and get_bond_by as the targeted alternatives. An agent can immediately tell this is a bulk reference dump, not a search or detail lookup.

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 explicitly says this is 'A dump for scripts, not something to read,' gives the reason (about 1,600 bonds and 2.4 MB of JSON, with INSTRUMENT_STATUS_ALL at 38 MB), and routes the agent to find_instrument with instrument_kind="bond" or get_bond_by for particular bonds. Both when-to-use and when-not-to-use are covered with concrete alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.