Skip to main content
Glama

finwire.pl - Polish financial data

Tourism pressure in Polish municipalities (finwire_tourism_pressure)

get_tourism_pressure
Read-onlyIdempotent

Use for tourism in a Polish municipality, county or province: bed places per 1000 residents, nights spent, tourists, bed occupancy by month, and where short-term rental pressure is highest. Presja turystyczna finwire (finwire_tourism_pressure) from Statistics Poland (GUS BDL): bed places in tourist accommodation on 31 July per 1000 residents for Poland and each municipality with its rank; nights spent and tourists per year (Poland, provinces, counties, nights per resident), nights and bed occupancy rate per month (Poland, provinces). With q: municipalities matching the name, with the county nights per resident. GUS has no nights for municipalities after 2014.

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

Input Schema

NameRequiredDescriptionDefault
qNoPart of a municipality name, e.g. Zakopane; omit for Poland, provinces and the top municipalities.

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.2/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 the safety profile is covered. The description adds real behavioral context beyond that: which metrics exist at which geographic level, default behavior when q is omitted, and the hard limit that GUS has no municipality-level nights after 2014.

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

Conciseness3/5

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

The purpose is front-loaded well, but the definition repeats the tool name twice ('Presja turystyczna finwire (finwire_tourism_pressure)'), duplicating the title and name with no added information, and the per-metric geography parentheticals make the middle dense. It is informative but not tight.

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?

With an output schema present, return values need not be explained, and the description covers granularity per metric, default scope, and the 2014 data limitation. Only the overall time coverage of the non-municipal series is left unspecified.

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% and the single q parameter is already documented, so the baseline is 3. The description still adds meaning: a name match also returns the corresponding county's nights per resident, and the county/province roll-up behavior differs by metric.

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?

Names a specific resource (tourism pressure indicators for Polish municipalities, counties and provinces), enumerates the exact measures returned (bed places per 1000 residents, nights spent, tourists, monthly bed occupancy, short-term rental pressure) and identifies the source (GUS BDL). This makes it unmistakable against sibling datasets such as get_bank_rates or get_eu_gdp.

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

Usage Guidelines4/5

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

Opens with an explicit 'Use for tourism in a Polish municipality, county or province' and explains the two usage modes: pass q to match municipality names, omit q for Poland/provinces/top municipalities. No explicit when-not or named alternatives, which keeps it below a 5.

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.