German real-time fuel prices (Benzinpreise) for all German gas stations, sourced from the official MTS-K (Markttransparenzstelle fuer Kraftstoffe) via creativecommons.tankerkoenig.de
Three well-defined tools with complete input schemas, clear descriptions, and proper enum constraints. Tool names follow verb_noun pattern (stations_nearby, station_details, prices). Descriptions are detailed (150-250 chars) and include examples. All parameters have types and descriptions. However, output schemas are not documented, LLMs cannot see what fields to expect in responses. Error handling is present but generic. No tool annotations (readOnlyHint, idempotentHint). Missing pagination guidance for potentially large result sets.
Bulk current fuel prices (E5, E10, diesel in EUR per liter) for up to 10 German gas stations by station id — the efficient refresh call for price-watch and price-alert flows once station ids are known. MTS-K real-time Benzinpreise, Germany only. Example: tankerkoenig_prices({ station_ids: ["94e70fc4-b22f-4e5a-877f-bc1082cdae81", "278130b1-e062-4a0f-80cc-19e486b4c024"] })
Full detail for one German gas station by its Tankerkoenig station id (UUID from tankerkoenig_stations_nearby): opening times, current E5 / E10 / diesel prices in EUR per liter, brand, address, state, and open status. MTS-K real-time data, Germany only. Example: tankerkoenig_station_details({ station_id: "94e70fc4-b22f-4e5a-877f-bc1082cdae81" })
German gas station fuel prices near a location — Benzinpreise Germany, real-time from the official MTS-K feed. Find the cheapest diesel, E5, or E10 near a point in Germany with price in EUR per liter, brand, address, distance, and open status. Coordinates are required: geocode a German city or address first (e.g. via a geocoding tool) — Berlin is lat 52.52, lng 13.40. Data covers Germany only. Example: tankerkoenig_stations_nearby({ latitude: 52.52, longitude: 13.40, radius_km: 5, fuel: "diesel", sort: "price" })
Output schemas not documented. LLMs cannot see what fields (price, brand, address, distance, open_status, etc.) are returned. This forces agents to guess field names for downstream processing and risks hallucinated field access.
No tool annotations. Tools are read-only and idempotent, but lack readOnlyHint and idempotentHint annotations. This prevents agents from reasoning about safety and retry behavior.
API key exposed as tool parameter (_apiKey). Although marked optional with server-side injection hint, best practice is to remove it entirely from the schema and inject server-side only. Secrets in parameters risk logging and trace leakage.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
No pagination or result limit guidance. tankerkoenig_stations_nearby with radius_km=25 could return hundreds of stations. No mention of max results, pagination tokens, or offset/limit parameters. Large responses risk context window exhaustion.
Error messages are generic. checkApiError() returns 'Tankerkoenig {tool} error: {msg}' without recovery guidance. LLMs need actionable next steps: 'Try with a different location', 'Retry in 60 seconds', or 'Check your API key'.