Skip to main content
Glama

Obligacje Catalyst (Obligacyjny Inwestor)

Calendar of maturities, coupons and offers

get_calendar
Read-onlyIdempotent

Calendar of the Catalyst corporate bond market for a date range: maturities (redemptions), interest payments and open public offers. Default range: next 30 days; maximum 366 days and 100 rows per call. Kalendarz wykupów, wypłat odsetek i zapisów na emisje.

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_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD (default: from + 30 days).
fromNoStart date YYYY-MM-DD (default: today).
typeNoWhich events to return (default: maturities).
issuerNoOptional issuer name or id to filter by.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds concrete operational limits: a maximum span of 366 days and 100 rows per call, and a default range of the next 30 days. These caps are genuinely useful context that the annotations do not supply.

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 core content is front-loaded and compact: the tool scope, event types, defaults, and hard limits come first. The closing Polish sentence duplicates the title and scope in another language, which is mildly redundant for an agent but cheap and potentially useful for matching against Polish-language queries.

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 four-parameter, read-only lookup with full schema coverage, the description covers scope, defaults, and caps, which is enough to call it correctly. Since there is no output schema, it could have described the response shape, though the event framing ('maturities, interest payments, offers') gives a reasonable expectation of what is returned.

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 description coverage is 100%, so the schema already documents 'from', 'to', 'type', and 'issuer', including the enum values and defaults. The description reinforces the date-range semantics and the default window but adds almost no new parameter meaning beyond what the schema provides, so the baseline of 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 names a specific verb and resource: a calendar of the Catalyst corporate bond market covering maturities, interest payments, and open public offers. This is clear enough to distinguish it from siblings such as get_bond and search_issuers, but it never explicitly contrasts itself with them, so it falls short of the top score.

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?

The description implies usage as an event-listing tool over a date range, and it states the default window is the next 30 days. However, it gives no explicit when-to-use or when-not-to-use guidance, nor does it route the agent to alternatives when a specific bond or issuer is needed.

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