TankoUp

Petrol station details

get_station_details

Read-only

Everything about one petrol station: every fuel's current price, opening hours, address and links.

Input Schema

Name	Required	Description
`lat`	No	Optional: the user's latitude, for the distance.
`lng`	No	Optional: the user's longitude.
`station_id`	Yes	Station id from another TankoUp tool, like 'ES-3213'.

Output Schema

Name	Required	Description	Default
`id`	Yes
`lat`	Yes
`lng`	Yes
`name`	Yes
`town`	Yes
`brand`	Yes
`prices`	Yes
`address`	Yes
`open_now`	Yes	null when the opening hours are unknown.
`province`	Yes
`distance_km`	Yes	From the given lat/lng, straight line. null without them.
`tankoup_url`	Yes
`app_store_url`	No	The TankoUp app for iPhone.	https://apps.apple.com/es/app/tankoup/id6789885475
`opening_hours`	Yes	null when unknown.
`directions_url`	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

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

B3.4/5.0

Behavior3/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 adds which data categories come back, but says nothing about whether distance is computed when lat/lng are supplied, freshness of price data, or failure behavior for unknown ids.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single front-loaded sentence with zero filler; every clause names a distinct content category the agent will receive.

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 an output schema, full parameter documentation and safety annotations, the description is nearly complete for a read-only detail lookup. The one real gap is not stating the search-then-detail workflow that would tell an agent when to reach for this tool over its siblings.

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 schema already explains station_id format, lat/lng ranges and their purpose. The description adds no parameter-level meaning beyond that baseline, though it also does not mislead.

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?

States a clear resource and enumerates what it returns: fuel prices, opening hours, address and links for a single station. The phrase 'one petrol station' implicitly separates it from the aggregate/search siblings (find_cheapest_fuel_nearby, get_province_fuel_prices), but it never names them explicitly.

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 when-to-use guidance and no alternatives are mentioned. The reader must infer that this is the follow-up call after a search tool returns a station id; that workflow hint lives only in the station_id schema description, not in the tool description.

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.