pumperly-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUMPERLY_ORIGIN | No | Pumperly origin country |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_routeC | Calculate a driving route between two points |
| find_nearest_stationsC | Find fuel stations nearest to a coordinate |
| find_route_stationsC | Find fuel stations along a route corridor |
| geocodeB | Search for a location by name (geocoding) |
| get_stations_in_areaB | Get fuel stations within a bounding box |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| App configuration | Countries, defaults, and fuel types supported by Pumperly |
| ECB exchange rates | Daily exchange rates from the European Central Bank |
| Platform statistics | Station and price counts per country |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: route calculation, finding stations by proximity, along a route, geocoding, and area-based search. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., calculate_route, find_nearest_stations). Even 'geocode' is a conventional single word verb. No mixing of styles.
With 5 tools, the set is well-scoped for a fuel station and routing service. Each tool provides essential functionality without redundancy or unnecessary complexity.
Core operations are covered: geocoding, route calculation, and three ways to find stations. Minor gaps like station details (prices, amenities) or reverse geocoding are not critical for the primary use case.