Skip to main content
Glama

finwire.pl - Polish financial data

Maximum fuel prices

get_fuel_prices
Read-onlyIdempotent

Use for the maximum fuel prices that the state sets. For average prices in shops, use get_retail_prices. Maximum retail prices of Pb95, Pb98 and diesel in PLN per litre announced by the Minister of Energy in Monitor Polski: price in force, next day price if announced, and recent history.

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

Input Schema

NameRequiredDescriptionDefault
historyNoNumber of past announcements, default 7.

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. First observed

TDQS

A4.4/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 genuinely new behavior context: the data source is a ministerial announcement, the payload includes the price in force plus a next-day price only if announced, and a history window. It stops short of saying how often announcements refresh or what happens when no next-day price exists, 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.

Conciseness4/5

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

Three short sentences, front-loaded with the routing rule before the data details, with no filler. There is mild redundancy between the opening 'maximum fuel prices' and the later 'Maximum retail prices of Pb95...', but the second instance earns its place by adding currency, units and product names.

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 single-parameter read tool with full schema coverage, complete safety annotations and an output schema, the description supplies everything an agent still needs: the source of truth, the precise content of the response, and the alternative tool for a different notion of 'fuel price'.

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% and the single 'history' parameter already documents its meaning and default of 7. The description only echoes this via 'recent history' and adds no extra semantics such as what a value of 0 returns. Baseline 3 is appropriate when the schema does the work.

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 verb and resource ('maximum fuel prices that the state sets') and then enumerates exactly what is returned: Pb95, Pb98 and diesel maxima in PLN per litre. It names the sibling it is not (get_retail_prices) and the issuing authority (Minister of Energy, Monitor Polski), so an agent can distinguish it without opening any 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 routing rule: use this for state-set maximum prices, use get_retail_prices for average shop prices. The condition that selects between the two alternatives is stated directly rather than implied.

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.