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

T-Bank Invest MCP Server (read-only)

by Sicness

get_bond_by

Read-only

Fetch bond details—maturity date, coupon rate, nominal, accrued interest, issue size, and risk—by ticker, FIGI, ISIN, or UID; auto-detects ID type.

Instructions

Get detailed bond info: maturity date, coupon rate, nominal, ACI, issue size, risk level.

Args: id: Bond ticker, FIGI, ISIN or UID — which one it is gets recognised automatically id_type: Only needed with class_code: INSTRUMENT_ID_TYPE_TICKER. Otherwise leave the default. class_code: Board of a ticker (e.g. "TQBR"), to pick one listing out of several

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": {
      "id": "<id>"
    },
    "name": "get_bond_by"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
id_typeNoINSTRUMENT_ID_TYPE_FIGI
class_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds one genuine operational nuance — that the id format (ticker/FIGI/ISIN/UID) is auto-detected — but says nothing about pagination, error behavior, or how multiple listings are resolved.

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 returned-field list is front-loaded in sentence one, followed by a compact Args block for the three parameters. No filler or repetition; it could be marginally tighter but every line earns its place.

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 no output schema, the description usefully enumerates the returned fields, and it covers all input parameters at 0% schema coverage. Gaps remain around listing disambiguation, error cases, and the behavior of non-ticker id types, but nothing essential to invoking the tool 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 must carry the burden, and it does document all three params: id accepts ticker/FIGI/ISIN/UID, id_type is only needed with INSTRUMENT_ID_TYPE_TICKER, and class_code selects a board (e.g. "TQBR"). It slightly under-describes the other three enum values and is mildly in tension with the FIGI default, but overall it compensates well for the empty schema.

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 opens with a specific verb+resource ('Get detailed bond info') and enumerates the returned fields (maturity date, coupon rate, nominal, ACI, issue size, risk level), so an agent knows exactly what this tool produces. It does not explicitly differentiate itself from nearby siblings like get_bond_coupons, get_bond_events, or get_instrument_by, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: the tool fetches a bond's detail profile, so an agent infers it should be called when bond detail is needed. There is no statement of when to prefer this over get_instrument_by, find_instrument, list_bonds, or the more specialized get_bond_coupons/get_bond_events, and no prerequisites or exclusions are given.

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