Skip to main content
Glama

finwire.pl - Polish financial data

Polish economy snapshot

get_macro_snapshot
Read-onlyIdempotent

Use for a general view of the Polish economy or a briefing. For one indicator, use get_macro_indicator. Returns the six headline indicators (GDP, inflation, unemployment, wages, rates and similar) with latest reading, change and freshness, which indicators changed recently, and the next releases and RPP meetings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
asOfNo
sourceNo
docsUrlNo
citationYes
headlineYes
upcomingYes
serverDateYes
recentlyChangedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine behavioral context the annotations cannot: the contents of the payload (six headline indicators with latest reading, change, freshness), change flags, and forward-looking items (next releases, RPP meetings). It stops short of stating caching, rate limits, or update cadence, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the primary use case, then the exclusion, then the payload summary. Every sentence carries distinct information and none repeats the title or annotations.

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?

A zero-parameter tool with an output schema and full annotation coverage needs little, yet the description still characterizes the return contents so an agent can judge fit before calling. The only soft spot is "and similar" leaving the sixth indicator slightly open, but the output schema resolves that.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It correctly avoids inventing filtering options that do not exist, which itself prevents an agent from attempting argument-based narrowing.

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 concrete verb-and-resource pairing (a snapshot of the Polish economy) and immediately scopes it as a "general view" or "briefing." It also names the sibling get_macro_indicator as the single-indicator path, so an agent can separate the two tools without inspecting 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?

Gives an explicit when-to-use (general overview/briefing) and an explicit when-not-to-use with the alternative named ("For one indicator, use get_macro_indicator"). The routing condition is fully determined by the description text.

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.