Skip to main content
Glama

Obligacje Catalyst (Obligacyjny Inwestor)

Details of one bond series

get_bond
Read-onlyIdempotent

Details of one Catalyst bond series by its code (e.g. "KRU1226"): ISIN, issuer, maturity, coupon terms, collateral, issue value, upcoming interest payment dates and the financial covenant from the terms of issue with a quote and source document, plus data_quality per field (confirmed by a document, to verify, missing). Szczegóły serii: parametry, terminy odsetek, kowenant, jakość danych.

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": {
      "code": "<code>"
    },
    "name": "get_bond"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCatalyst code of the series, e.g. "KRU1226".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 safety is covered. The description adds real context beyond that: the data_quality field's three-state semantics (confirmed by a document, to verify, missing) and the fact that covenant data comes with a quote and source document. It does not say what happens when the code is unknown, which is the main remaining gap.

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 field enumeration is front-loaded and informative, but the description then repeats the entire content in a single Polish sentence, which is redundant for an agent that has already parsed the English list. The long comma-separated clause listing every returned field also makes the sentence harder to scan than a short purpose statement followed by a breakdown.

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?

There is no output schema, so the description must carry the return-value burden, and it does so thoroughly by naming each returned section and the meaning of data_quality. For a one-parameter read tool with full annotation coverage, only the not-found/error behavior is left unstated.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single 'code' parameter, and the schema already carries the example "KRU1226", which the description merely repeats. No additional meaning — format constraints, alternate identifiers like ISIN, or case sensitivity — is layered on top of the schema, so baseline 3 applies.

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 gives a specific verb+resource ('details of one Catalyst bond series by its code') and enumerates the exact payload: ISIN, issuer, maturity, coupon, collateral, issue value, interest dates, covenant with quote and source document, plus data_quality. That is far more concrete than the title alone. It never names a sibling such as get_issuer_bonds or search_issuers, so the differentiation is implicit rather than stated.

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 by 'by its code' — an agent can infer this is the single-series lookup when a Catalyst code is already known. There is no explicit when-not-to-use or routing to get_issuer_bonds for listings or search_issuers for discovery, leaving the agent to infer the boundary from tool names.

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