TankoUp

Fuel prices in a province

get_province_fuel_prices

Read-only

Average and lowest fuel prices in a Spanish province, with its cheapest stations.

For each fuel: the average and lowest price per litre, the change over the
last 30 days, how it compares with the Spanish average, the cheapest brand
and the 3 cheapest stations.

Input Schema

Name	Required	Description	Default
`fuel`	No	Fuel type: diesel = Gasóleo A (regular diesel), diesel_premium = Gasóleo Premium, sp95 = Gasolina 95 E5 (regular unleaded petrol), sp95_e10 = Gasolina 95 E10, sp98 = Gasolina 98, lpg = GLP / autogas. Leave out for every fuel.
`province`	Yes	One of Spain's 50 provinces, or Ceuta or Melilla, in Spanish, English or the regional language: 'Córdoba', 'Vizcaya', 'Illes Balears', 'Seville'.

Output Schema

Name	Required	Description	Default
`fuels`	Yes
`province`	Yes
`app_store_url`	No	The TankoUp app for iPhone.	https://apps.apple.com/es/app/tankoup/id6789885475
`google_play_url`	No	The TankoUp app for Android.	https://play.google.com/store/apps/details?id=com.tankoup.app&referrer=utm_source%3Dmcp%26utm_medium%3Dassistant
`more_on_tankoup`	Yes
`prices_updated_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedOutput schema / properties / app_store_url

Added value: +{
+  "default": "https://apps.apple.com/es/app/tankoup/id6789885475",
+  "description": "The TankoUp app for iPhone.",
+  "title": "App Store Url",
+  "type": "string"
+}

addedOutput schema / properties / google_play_url

Added value: +{
+  "default": "https://play.google.com/store/apps/details?id=com.tankoup.app&referrer=utm_source%3Dmcp%26utm_medium%3Dassistant",
+  "description": "The TankoUp app for Android.",
+  "title": "Google Play Url",
+  "type": "string"
+}

First observedNov 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes beyond that by enumerating the per-fuel payload: average and lowest price per litre, 30-day change, comparison with the Spanish average, cheapest brand, and the 3 cheapest stations. It does not say how fresh the prices are or where they come from, which is the main remaining gap for a data tool.

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?

It is three short, front-loaded sentences with no filler: scope first, then the returned metrics. The 'For each fuel:' enumeration is slightly list-like but every item carries information an agent cannot get without calling the tool.

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?

An output schema exists, so return structure needn't be explained, and annotations cover the read-only nature. Given two well-documented parameters, the description is nearly complete; only data source/freshness of the price figures is unaddressed.

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%: the fuel parameter lists each code with its Spanish name and states that omitting it returns every fuel, and the province parameter lists accepted spellings. The description adds no further meaning about the parameters, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Average and lowest fuel prices in a Spanish province') plus the scope differentiator versus siblings: it is a province-wide aggregate with 'its cheapest stations', not a proximity or route search. An agent can tell it apart from find_cheapest_fuel_nearby, find_cheapest_fuel_on_route and get_station_details 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 Guidelines3/5

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

Usage is implied by geographic scope (province-level statistics), but the description never states when to pick this over the sibling tools, nor any prerequisites or exclusions. A one-line contrast such as 'use find_cheapest_fuel_nearby for a point location' would make this explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TankoUp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.