Skip to main content
Glama

finwire.pl - Polish financial data

List Polish macroeconomic indicators

list_macro_indicators
Read-onlyIdempotent

Use first to find the key of a macro indicator. Then use get_macro_indicator with that key. Find indicators and their keys. Latest reading, change, next release and source for GDP, CPI and core inflation, unemployment, wages, retail sales, industrial output, NBP rates, FX, consumer sentiment, mortgage market and statutory limits. Filter by group or free text (Polish or English words, e.g. "inflacja", "wages"). Set include_descriptions to learn what each series measures when keys look alike (cpi-rr vs hicp-rr).

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

Input Schema

NameRequiredDescriptionDefault
groupNoIndicator group.
queryNoCase-insensitive text matched against key and label.
include_descriptionsNoAdd a one-sentence explanation per indicator. Default false.

Output Schema

NameRequiredDescriptionDefault
asOfNo
countYes
sourceNo
docsUrlNo
citationYes
indicatorsYes
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.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 needs no restatement here. The description adds real context beyond them: the payload shape (latest reading, change, next release, source) and the fact that filtered queries are language-agnostic, though it does not discuss pagination or result limits.

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 workflow instruction is correctly front-loaded in the first two sentences, and the rest is dense and scannable. The sentence 'Find indicators and their keys' partially repeats the opening line, and the long domain list is padding-adjacent, though it doubles as scope documentation.

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 an output schema present, the description needn't explain return values, and it does not waste effort doing so. For a three-optional-parameter list tool with full annotation coverage, it supplies everything an agent needs: the workflow, filtering semantics, and the disambiguation technique.

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 is 3, but the description earns a step up by adding meaning the schema lacks: query matching works on Polish or English words (with 'inflacja'/'wages' examples) and include_descriptions exists specifically to disambiguate similar keys like cpi-rr versus hicp-rr.

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?

The description states a specific verb and resource ('find the key of a macro indicator', 'Find indicators and their keys') and enumerates the covered domains (GDP, CPI, unemployment, NBP rates, FX, etc.), which lets an agent distinguish it from get_macro_indicator, the per-indicator lookup, without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit sequencing rule ('Use first ... Then use get_macro_indicator with that key') and names a concrete conditional for include_descriptions ('when keys look alike'), plus how to filter by group or free text. This is a when-to-use plus a named alternative rather than an implied workflow.

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.