Skip to main content
Glama

Petrol and diesel prices

get_fuel_prices
Read-onlyIdempotent

The latest weekly consumer pump price of petrol (Euro-super 95) and diesel in one EU country, in euro per litre including taxes, from the European Commission's Weekly Oil Bulletin: the change on the previous week and on a year earlier, the price in the national currency for countries outside the euro, and the EU average and the cheapest and most expensive country of the same week.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "get_fuel_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelNopetrol (Euro-super 95) or diesel. Omit for both.
countryYesISO 3166-1 alpha-2 country code (Greece is GR), or EA for the euro area, or EU for the European Union. The bulletin covers the 27 EU member states and the two averages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description's real added value is data provenance and payload shape: weekly cadence, tax-inclusive euro pricing, week-over-week and year-over-year change, national-currency values for non-euro countries, plus EU average and cheapest/priciest country. It says nothing about how non-covered inputs are handled or data latency, so this is solid but not rich.

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?

Front-loaded with the core answer (what, where, units, source) then enumerates the returned components with no filler. It is a single sprawling sentence whose trailing list makes it harder to scan, which keeps it off a 5.

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?

Two 100%-documented enum parameters, annotations covering safety, and no output schema means the description is responsible for describing returns, which it does thoroughly. Only minor gaps remain around edge behavior for unsupported country codes and data freshness.

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 both parameters are documented enums, so the schema carries the parameter burden; baseline 3 applies. The description adds some meaning by tying the country parameter to the currency behavior (national currency outside the euro) and the euro-area/EU averages, but it never explains the useful 'omit fuel for both' default, which only the schema provides.

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 (weekly consumer pump price of petrol Euro-super 95 and diesel), scope (one EU country), units and tax basis (euro per litre including taxes), and source (European Commission Weekly Oil Bulletin). This is unambiguous against siblings like get_electricity_spot_prices or get_inflation 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 Guidelines2/5

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

No explicit when-to-use or when-not guidance and no alternative named; the agent must infer from 'one EU country' that compare_countries is the multi-country path. Usage is only implied by the scope phrase, which is below the 'clear context' bar.

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.

Resources