fuel-prices-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fuel_find_cheapestA | Find the cheapest fuel near a location, ranked by price, with each station's price compared to the local median. Prices are pence per litre from the official Fuel Finder data (updated within 30 minutes). |
| fuel_nearby_stationsA | List forecourts near a location (nearest first) with all their fuel prices, brand, amenities and motorway/supermarket flags. |
| fuel_area_summaryA | Per-fuel price statistics for an area: min/median/max and the cheapest station for each fuel. Use it to judge whether a price you've seen is actually good locally. |
| fuel_data_statusA | Check the server's data: credentials configured, stations loaded, and cache age. Use this to diagnose empty results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: one diagnoses server/data status, one finds the cheapest station, one lists nearby stations with full details, and one provides area-level price statistics. No two tools would be confused for each other.
Tools consistently follow a 'fuel_' prefix with descriptive noun phrases (status, find_cheapest, nearby_stations, area_summary). The pattern is mostly consistent, though 'find_cheapest' uses a verb while 'nearby_stations' and 'area_summary' use noun phrases, which is a minor stylistic deviation.
Four tools is well-scoped for a fuel-prices domain: diagnostics, cheapest search, station listing, and area statistics each earn their place. This is a tight, focused set with no padding.
The set covers the core workflows: finding cheap fuel, listing nearby stations, and evaluating prices against area statistics, plus a diagnostic tool for troubleshooting. A minor gap is the absence of a direct single-station detail lookup or fuel-type-specific filtering, but most common user needs are covered.