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

T-Bank Invest MCP Server (read-only)

by Sicness

get_bond_coupons

Read-only

Retrieve a bond's coupon payment schedule, including dates, amounts, and coupon periods, for a ticker, FIGI, ISIN, or UID, with optional from/to date filters.

Instructions

Get bond coupon payment schedule: dates, amounts, coupon periods.

Args: figi: Deprecated, kept for existing callers — pass the FIGI as instrument_id instead instrument_id: Bond ticker, FIGI, ISIN or UID (required) from_date: Start date (YYYY-MM-DD), default: now to_date: End date (YYYY-MM-DD, inclusive), default: 1 year from now

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

Input Schema

NameRequiredDescriptionDefault
figiNo
to_dateNo
from_dateNo
instrument_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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. The description adds default date-range behavior and inclusivity, plus a deprecation warning, but omits things like pagination, result limits, or auth requirements.

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?

One front-loaded sentence states what is returned, followed by a compact args block with no filler. Every line earns its place, and nothing is redundant given the empty schema descriptions.

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?

For a 4-param tool with zero schema coverage and no output schema, the description supplies formats, defaults, and deprecation guidance needed to invoke it correctly, and it sketches the return shape. Only minor gaps remain (no pagination/limit expectations).

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

Parameters5/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 full burden — and it does: it documents all four params including the accepted instrument_id formats (ticker, FIGI, ISIN, UID), date format YYYY-MM-DD, inclusive to_date, defaults, and the deprecated figi. This fully compensates for the schema gap.

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 names a specific verb and resource — 'Get bond coupon payment schedule' — and enumerates the returned content (dates, amounts, coupon periods). This is clearly distinguishable from siblings like get_bond_events, though it doesn't explicitly reference them.

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

Usage Guidelines2/5

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

No guidance on when to choose this over get_bond_by, get_bond_events, or get_accrued_interests. The only directional hint is internal (use instrument_id instead of the deprecated figi), which is a parameter note rather than tool-selection guidance.

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