Skip to main content
Glama

finwire.pl - Polish financial data

Fuel prices in EU countries (European Commission)

get_eu_fuel_prices
Read-onlyIdempotent

Use for fuel prices in other EU countries, Poland against the EU, and where to fill the tank on a trip abroad. Say that the prices are national averages. Prices of Euro-super 95 petrol, diesel, LPG or heating oil at filling stations in the 27 EU countries from the European Commission Weekly Oil Bulletin (Monday prices, weekly since 2005): PLN and EUR per litre with all taxes, without taxes and tax share, rank from the cheapest, weekly change, a year earlier, the EU and euro area weighted averages, the difference for a full tank against Poland and the finwire index finwire_eu_fuel_price_gap. PLN prices use the NBP EUR mid rate of the reading day. These are national averages; motorway stations are usually more expensive.

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

Input Schema

NameRequiredDescriptionDefault
fuelNoFuel, default euro95.
tankNoTank size in litres for the full-tank difference, default 50.
countryNoEU country code (Eurostat, Greece = EL) to compare 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

A3.6/5.0
Behavior3/5

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

The annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description's job is to add data provenance and quirks. It does that well (Monday prices weekly since 2005, PLN converted using the NBP EUR mid rate of the reading day, inclusion of the finwire_eu_fuel_price_gap index), but the caveat about national averages is stated twice and nothing is said about freshness lag or coverage gaps for countries not in the bulletin.

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 usage sentence is well front-loaded, but the middle is a single sprawling sentence that dumps every output field (rank, weekly change, year earlier, weighted averages, gap index) rather than letting the output schema carry it. The national-averages disclaimer appears twice, which is wasted space.

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 read-only statistical lookup with a full output schema, the description supplies the provenance, currency-conversion basis, and comparison semantics an agent needs to interpret results correctly. Remaining gaps (refresh cadence versus publication date, behavior for non-EU or unsupported codes) are minor given the annotations and output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the enum values and defaults are already documented, which sets the baseline at 3. The description adds modest meaning by tying the tank parameter to 'the difference for a full tank against Poland' and the country parameter to the Poland comparison, but it does not explain the EL-vs-GR code convention or the valid ranges beyond what the schema states.

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 names a specific resource (Euro-super 95, diesel, LPG and heating oil prices at filling stations in the 27 EU countries) and a specific source (European Commission Weekly Oil Bulletin), which is far more than a restatement of the title. It implicitly separates itself from the domestic-sounding sibling get_fuel_prices by stressing 'other EU countries' and 'Poland against the EU', though it never names that sibling, so an agent must infer the split.

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 fuel prices in other EU countries, Poland against the EU, and where to fill the tank on a trip abroad' gives concrete use contexts up front. It stops short of explicit when-not guidance or naming an alternative tool, so the agent has to infer that domestic-only price queries belong elsewhere.

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.