Skip to main content
Glama

finwire.pl - Polish financial data

Government debt and deficit in the EU

get_eu_public_debt
Read-onlyIdempotent

Use for government debt and deficit of EU countries and Poland against the EU, and for the 3% and 60% of GDP reference values. For Polish State Treasury debt per month, use get_public_debt. General government gross debt, deficit and interest as % of GDP in the 27 EU countries, the EU and the euro area (Eurostat): debt at the end of the latest quarter with the change in a year, deficit, interest and debt in the latest year from the excessive deficit procedure notification, ranks, countries above the 3% deficit and 60% debt reference values in the data (not the list of countries under the procedure), annual history of Poland, the EU and one comparison country, and finwire_eu_debt_threshold_gap (Poland quarterly debt minus 60, percentage points).

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

Input Schema

NameRequiredDescriptionDefault
compareNoEU country code (Eurostat, Greece = EL) for the history and the comparison with Poland, default DE.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds substantive content disclosure beyond that: quarterly debt with year-over-year change, EDP notification figures, ranks, and a derived series finwire_eu_debt_threshold_gap (Poland quarterly debt minus 60pp). It does not discuss freshness/caching or response shape, but the output schema exists to carry return structure.

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 lead sentence is front-loaded with purpose and the sibling hand-off, which is exactly the right order. The second sentence is a long multi-clause inventory (ranks, EDP notification, history, derived metric) that is dense and partially duplicates the output schema, costing some readability.

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 parameterless-in-practice read tool with an output schema and full annotation coverage, the description supplies everything needed: data domain, geography, cadence (latest quarter vs latest year), the derived metric, and the boundary against the sibling. Nothing an agent needs to call it correctly is missing.

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?

There is a single optional parameter whose schema is fully documented, so the baseline is already 3. The description goes further by framing it functionally as 'one comparison country' paired with 'annual history of Poland, the EU', which tells the agent what the parameter actually changes in the output rather than just its format.

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 specific resource and scope ('government debt and deficit of EU countries and Poland against the EU') plus the exact reference values (3% and 60% of GDP) it serves. It explicitly separates itself from the sibling get_public_debt, so an agent can discriminate without opening schemas.

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 both a when-to-use and a when-not-to-use: EU/Poland-vs-EU debt and deficit here, monthly Polish State Treasury debt in get_public_debt instead. It also narrows the scope with the caveat that the ranking is of countries above the thresholds in the data, not the official excessive-deficit-procedure list.

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.