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

T-Bank Invest MCP Server (read-only)

by Sicness

get_bond_events

Read-only

Retrieve bond coupon payments, offers, maturity, amortization, and conversion events for an instrument, with optional type and date range filters.

Instructions

Get bond events: coupon payments, offers (calls), maturity, conversions.

Without dates the API returns only a window of a few years around today, so a bond's maturity or a distant offer needs an explicit from_date/to_date range to show up. A field of an event that is zero or empty is left out.

A coupon event carries couponInterestRate, the coupon's rate in percent a year — the bond itself (get_bond_by) does not have it. Partial repayments (amortization) come as MTY events with operationType "OA" and value in percent of the nominal; the final repayment is the MTY event with operationType "OM".

Args: instrument_id: Bond ticker, FIGI, ISIN or UID type: Event type filter (empty = all): CPN (coupon), CALL (offer), MTY (maturity and amortization), CONV (conversion) from_date: Start date (YYYY-MM-DD), default: chosen by the API to_date: End date (YYYY-MM-DD, inclusive), default: chosen by the API

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": {
      "instrument_id": "<instrument_id>"
    },
    "name": "get_bond_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
to_dateNo
from_dateNo
instrument_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavioral context beyond them: the default date window, that zero/empty event fields are omitted, and that amortization arrives as MTY events with operationType 'OA'/'OM'. It does not discuss rate limits or result size, but the added disclosure is substantial.

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?

Front-loaded with the core purpose, then progressively detailed behavioral notes and an Args block. Almost every sentence earns its place, though the OA/OM amortization detail is niche and the prose is dense.

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, the description compensates by describing returned event fields (couponInterestRate, operationType, value in percent of nominal) and the omission rule for empty fields. Nothing essential to correct invocation appears missing.

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 does so: instrument_id accepted formats (ticker/FIGI/ISIN/UID), each type enum value decoded, date format YYYY-MM-DD, inclusive to_date, and the API-chosen defaults. This exceeds what the bare schema conveys.

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+resource ('Get bond events') and enumerates the event classes (coupon, offer/call, maturity, conversion). It also explicitly distinguishes itself from the sibling get_bond_by by noting the latter lacks couponInterestRate. An agent can route correctly without opening a schema.

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?

Gives clear context: without dates the API returns only a window around today, so a distant maturity or offer requires an explicit range. It names get_bond_by for contrast, but does not mention the sibling get_bond_coupons or when that would be preferable, so the when-not guidance is incomplete.

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