Skip to main content
Glama

finwire.pl - Polish financial data

Coal price and waste fee in Poland

get_coal_waste_prices
Read-onlyIdempotent

Use for the average price of a tonne of coal or the waste collection fee, in Poland and by province. Cena węgla finwire (finwire_coal_price_pl) and Opłata za odpady finwire (finwire_waste_fee_pl): annual average price of a tonne of hard coal and monthly fee for sorted waste collection per person in multi-family buildings, Poland and 16 provinces, from Statistics Poland (GUS). Annual averages for a past year, not current shop prices.

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

Input Schema

NameRequiredDescriptionDefault
regionNoProvince slug without diacritics, e.g. mazowieckie, slaskie, kujawsko-pomorskie; default all 16.
seriesNocoal (default) or waste.

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that with data provenance (Statistics Poland/GUS), the annual-averaging caveat, and the 16-province coverage. It does not discuss return shape, but an output schema exists.

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 sentences, front-loaded with the use case, then the definitional detail. The interleaved Polish series names are slightly verbose but serve discoverability for Polish-language queries, and no sentence is purely redundant.

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?

For a two-parameter, read-only statistics lookup with an output schema, the description covers purpose, units, geographic scope, source and the key 'past year averages, not current prices' caveat. Only the absence of explicit sibling routing keeps it from being fully complete.

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 goes beyond the schema by explaining what each series actually measures: annual average price per tonne of hard coal versus a monthly sorted-waste fee per person in multi-family buildings. That unit and definition detail is not in the enum values and materially aids interpretation.

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 states a specific resource and scope: 'average price of a tonne of coal or the waste collection fee, in Poland and by province', plus the GUS provenance and the two underlying series names. It is clearly distinguishable from generic price tools in substance, though it never explicitly names a sibling such as get_energy_prices or get_fuel_prices to route an agent.

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?

'Use for...' gives direct when-to-use guidance, and 'Annual averages for a past year, not current shop prices' effectively excludes a plausible alternative (current pump/shop price tools). It stops short of naming a specific alternative tool to pick instead, so no explicit routing.

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.