Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_fuel_station_prices_de

Get current German fuel prices (Super E10, Super E5, Diesel, HVO100, Autogas LPG, AdBlue) and Bundeskartellamt MTS-K intraday cheapest refuel window.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fuel_station_prices_de"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoGerman city (e.g. Berlin, München, Köln, Hamburg)
fuel_typeNoFuel type: Super E10, Super E5, Diesel, HVO100, Autogas LPG, or AdBlue

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the data source (Bundeskartellamt MTS-K) and intraday freshness, but does not explain coverage (e.g., all Germany vs. a city), what the 'cheapest refuel window' contains, or the return format.

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?

The definition is a single front-loaded sentence with no filler. The parenthetical fuel list is somewhat long and duplicates schema information, but it still helps scope the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-style retrieval tool with two optional parameters and no output schema. The description states what data is retrieved but omits what the response looks like and how city filtering affects results, leaving an agent without full context for interpreting output.

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 both parameters are already documented in the input schema. The description repeats the fuel types but adds no meaningful semantics for the city parameter or optionality beyond what 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?

The description uses a specific verb ('Get') and resource ('current German fuel prices'), enumerates the supported fuel types, and adds the MTS-K cheapest refuel window. It clearly distinguishes this tool from the unrelated sibling tools.

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?

There is no explicit when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives or prerequisites. The purpose implies usage for current fuel prices, but the definition leaves all invocation context to inference.

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