TankoUp

Cheapest fuel near a place

find_cheapest_fuel_nearby

Read-only

Find the cheapest petrol stations in Spain near a town, city or point, for one fuel.

Returns the best stations by total cost (price plus the fuel used to get there), each with its price per litre, distance, whether it is open, and links to TankoUp and to directions.

Input Schema

Name	Required	Description
`lat`	No	Latitude of the search point.
`lng`	No	Longitude of the search point.
`fuel`	Yes	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.
`limit`	No	How many stations to return.
`place`	No	A Spanish town or city, optionally with its province: 'Lucena, Córdoba'. Use lat/lng instead for a street, landmark or the user's position.
`open_now`	No	Only stations open right now (unknown hours count as open).
`radius_km`	No	Search radius in km.

Output Schema

Name	Required	Description	Default
`fuel`	Yes
`place`	Yes	Where the search was centred, as understood.
`ranking`	Yes
`stations`	Yes	Best first, by total cost.
`radius_km`	Yes
`app_store_url`	No	The TankoUp app for iPhone.	https://apps.apple.com/es/app/tankoup/id6789885475
`stations_found`	Yes
`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
`area_average_eur_per_litre`	Yes
`best_saves_eur_on_40_litres`	Yes	Saving at the first station against the area average.
`other_places_with_this_name`	No

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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the description's contribution is the non-obvious ranking rule: stations are ordered by total cost, price plus the fuel burned to reach them. That is genuinely useful context an agent cannot infer from the schema, and it also discloses the returned fields, though it says nothing about what happens when no station is in radius.

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 short sentences, front-loaded with the purpose and followed by the return behavior. No wasted words or filler, though the trailing clause listing returned fields is somewhat redundant given an output schema exists.

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?

With annotations carrying the safety profile, a fully documented schema, and an output schema covering return values, the description only needs to add scope and ranking semantics, which it does. The main residual gap is that the Spain-only restriction and the cost-ranking assumption behind distances are implied rather than explained.

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 all seven parameters are already documented, including lat/lng versus place tradeoffs and the fuel enum labels. The description only echoes 'for one fuel' and adds no syntax, defaults, or interaction guidance beyond the schema, matching the baseline for fully documented schemas.

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?

It gives a specific verb and resource ('find the cheapest petrol stations') plus the geographic scope (Spain) and the anchor options (town, city or point). It stops short of explicitly distinguishing itself from the sibling find_cheapest_fuel_on_route, though 'near a town, city or point' implicitly contrasts with a route search.

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?

The phrase 'near a town, city or point' implies the intended use case but names no alternatives and states no exclusions. An agent must infer from the title and schema that the on-route sibling handles routes, and nothing explains when to prefer get_province_fuel_prices instead.

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.