Skip to main content
Glama

obrotomierz open data

Retail government bonds by country

get_retail_government_bonds_by_country
Read-only

Whether a country sells government bonds to individuals at issue and how they pay (inflation plus a fixed margin, market real rate, fixed, floating, step-up or prize), for all 195 countries, with the official source for each. Without a country: the number of countries in each category and the countries paying inflation plus a fixed margin.

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

Input Schema

NameRequiredDescriptionDefault
countryNoCountry name in English or Polish, or ISO 3166-1 alpha-2 code, e.g. "Hungary" or "HU"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral content beyond them: the 195-country scope, that each record carries its official source, the enumeration of payout categories, and the distinct aggregate response produced when the country argument is omitted.

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?

Two compact sentences, front-loaded with the core question the tool answers, then the no-argument behavior. The category list is dense but each item carries information; nothing reads as filler or repetition of the schema.

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?

For a one-optional-parameter read tool with full schema coverage, annotations and no output schema, the description covers both call modes, the domain scope and the shape of returned data. An agent can decide and invoke correctly without further information.

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 coverage is 100%, so the baseline would be 3, but the description goes further by making explicit that the country argument is optional and defining the exact aggregate returned in its absence (counts per category plus the list of countries paying inflation plus a fixed margin). That removes the main ambiguity a single optional parameter creates.

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 resource (retail government bonds sold to individuals at issue), the exact attributes returned (payout mechanics such as inflation plus fixed margin, market real rate, fixed, floating, step-up, prize), the coverage (all 195 countries) and provenance (official source per country). Scope also implicitly separates it from the Polish-bond and EU-bank-account siblings, though no sibling is named explicitly.

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 'Without a country:' clause effectively explains the two calling modes and what each returns, which is strong guidance for a single optional parameter. However, there is no statement about when to prefer this tool over the sibling Polish bond tools or what data is unavailable, so usage is implied rather than prescribed.

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