Skip to main content
Glama

Fuel or EV stations along a route line

find_route_stations
Read-onlyIdempotent

Find fuel stations and EV chargers along a given route line within a set corridor distance, sorted cheapest first by default, with each station's km along the route.

Instructions

List the fuel stations or EV chargers within corridor_km of a route line you already have, cheapest first by default, with each station's km along the route. Most callers want cheapest_fuel_on_route, which takes place names and does the routing too. Prices are per litre (per kg for CNG, LNG and H2, per kWh for EV) in local currency. The API allows 30 route searches per minute.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "geometry": "<geometry>",
      "fuel": "<fuel>"
    },
    "name": "find_route_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelYesFuel code. Common ones: B7 = diesel, E5 = petrol 95, E10 = petrol 95 E10, E5_98 = petrol 98, LPG = autogas, EV = charging. The pumperly://fuel-types resource lists all 16 with labels and price units.
limitNoHow many stations to return, 1 to 50. Default 10.
sort_byNoprice (cheapest first, default) or route (in driving order from the start).price
geometryYesGeoJSON LineString of the route: {"type":"LineString","coordinates":[[lon,lat],...]}, longitude first, 2 to 2000 points. calculate_route returns one with include_geometry=true.
corridor_kmNoHow far from the route a station may be, in km, 0.5 to 50. Default 5.

Output Schema

NameRequiredDescriptionDefault
fuelYes
unitYesWhat prices are per: L, kg or kWh
foundYes
centerNo
pricesYes
sort_byYes
returnedYes
stationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / corridor_km / default
      Added value: +5
    • changedInput schema / properties / corridor_km / description
      Previous value: -"Corridor width in kilometres (default 5)"New value: +"How far from the route a station may be, in km, 0.5 to 50. Default 5."
    • addedInput schema / properties / corridor_km / maximum
      Added value: +50
    • addedInput schema / properties / corridor_km / minimum
      Added value: +0.5
    • changedInput schema / properties / fuel / description
      Previous value: -"Fuel type code (e.g. B7, E5, E10, E85, LPG, CNG, LNG, EV)"New value: +"Fuel code. Common ones: B7 = diesel, E5 = petrol 95, E10 = petrol 95 E10, E5_98 = petrol 98, LPG = autogas, EV = charging. The pumperly://fuel-types resource lists all 16 with labels and price units."
    • addedInput schema / properties / fuel / enum
      Added value: +[
      +  "B7",
      +  "B7_PREMIUM",
      +  "B10",
      +  "B_AGRICULTURAL",
      +  "HVO",
      +  "E5",
      +  "E5_PREMIUM",
      +  "E10",
      +  "E5_98",
      +  "E98_E10",
      +  "LPG",
      +  "CNG",
      +  "LNG",
      +  "H2",
      +  "EV",
      +  "ADBLUE"
      +]
    • changedInput schema / properties / geometry / description
      Previous value: -"GeoJSON LineString as a JSON string, e.g. {\"type\":\"LineString\",\"coordinates\":[[lon,lat],...]}"New value: +"GeoJSON LineString of the route: {\"type\":\"LineString\",\"coordinates\":[[lon,lat],...]}, longitude first, 2 to 2000 points. calculate_route returns one with include_geometry=true."
    • addedInput schema / properties / geometry / properties
      Added value: +{
      +  "coordinates": {
      +    "items": {
      +      "items": {
      +        "type": "number"
      +      },
      +      "maxItems": 2,
      +      "minItems": 2,
      +      "type": "array"
      +    },
      +    "maxItems": 2000,
      +    "minItems": 2,
      +    "type": "array"
      +  },
      +  "type": {
      +    "enum": [
      +      "LineString"
      +    ],
      +    "type": "string"
      +  }
      +}
    • changedInput schema / properties / geometry / type
      Previous value: -"string"New value: +"object"
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 10,
      +  "description": "How many stations to return, 1 to 50. Default 10.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / sort_by
      Added value: +{
      +  "default": "price",
      +  "description": "price (cheapest first, default) or route (in driving order from the start).",
      +  "enum": [
      +    "price",
      +    "route"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "center": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "city": {
      +          "type": "string"
      +        },
      +        "country": {
      +          "type": "string"
      +        },
      +        "lat": {
      +          "type": "number"
      +        },
      +        "lon": {
      +          "type": "number"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "state": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "lat",
      +        "lon"
      +      ],
      +      "type": [
      +        "null",
      +        "object"
      +      ]
      +    },
      +    "found": {
      +      "type": "integer"
      +    },
      +    "fuel": {
      +      "type": "string"
      +    },
      +    "prices": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "count": {
      +            "type": "integer"
      +          },
      +          "currency": {
      +            "type": "string"
      +          },
      +          "max": {
      +            "type": "number"
      +          },
      +          "median": {
      +            "type": "number"
      +          },
      +          "min": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "currency",
      +          "count",
      +          "min",
      +          "median",
      +          "max"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "returned": {
      +      "type": "integer"
      +    },
      +    "sort_by": {
      +      "enum": [
      +        "price",
      +        "distance",
      +        "route"
      +      ],
      +      "type": "string"
      +    },
      +    "stations": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "address": {
      +            "type": "string"
      +          },
      +          "brand": {
      +            "type": "string"
      +          },
      +          "city": {
      +            "type": "string"
      +          },
      +          "country": {
      +            "description": "ISO 3166-1 alpha-2 country code",
      +            "type": "string"
      +          },
      +          "currency": {
      +            "description": "ISO 4217 currency of price",
      +            "type": "string"
      +          },
      +          "distance_km": {
      +            "description": "Straight-line distance from the search point, km",
      +            "type": [
      +              "null",
      +              "number"
      +            ]
      +          },
      +          "ev_fees": {
      +            "additionalProperties": true,
      +            "type": "object"
      +          },
      +          "lat": {
      +            "type": "number"
      +          },
      +          "lon": {
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "power_kw": {
      +            "description": "EV only: maximum charging power, kW",
      +            "type": [
      +              "null",
      +              "number"
      +            ]
      +          },
      +          "price": {
      +            "description": "Price per unit in currency",
      +            "type": [
      +              "null",
      +              "number"
      +            ]
      +          },
      +          "reported_at": {
      +            "description": "When the price was last reported (RFC 3339)",
      +            "type": "string"
      +          },
      +          "route_km": {
      +            "description": "Distance along the route from its start, km",
      +            "type": [
      +              "null",
      +              "number"
      +            ]
      +          },
      +          "unit": {
      +            "description": "What the price is per: L, kg or kWh",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "lat",
      +          "lon"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "unit": {
      +      "description": "What prices are per: L, kg or kWh",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "fuel",
      +    "unit",
      +    "sort_by",
      +    "found",
      +    "returned",
      +    "prices",
      +    "stations"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description adds context they cannot: the 30 route searches per minute rate limit and the price unit conventions (per litre, per kg for CNG/LNG/H2, per kWh for EV). These are behavioral facts an agent needs and cannot infer from the structured fields.

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?

Four sentences, each carrying distinct information: scope, alternative, units, rate limit. The key constraint and the sibling redirect are front-loaded, and nothing is repeated from the title or schema verbatim.

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

Completeness5/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 values need not be described. For a 5-parameter tool with nested geometry, the description covers the prerequisite input, the alternative tool, unit semantics, and throughput limits — nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by spelling out the price-unit mapping per fuel family, which the schema only gestures at via a resource reference. It adds less on geometry/corridor_km/limit, which the schema already documents thoroughly.

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?

States a specific verb and resource (list fuel stations / EV chargers), plus the scoping constraint (within corridor_km of a route line you already have), the default ordering, and the per-station 'km along route' output. This is enough to tell it apart from cheapest_fuel_on_route and get_stations_in_area 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 Guidelines5/5

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

Explicitly routes most callers to the sibling: 'Most callers want cheapest_fuel_on_route, which takes place names and does the routing too.' Combined with 'a route line you already have', it states both the prerequisite for using this tool and the condition that selects the alternative.

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