fuel-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.
SIMULATED: these are made-up stations, not real ones. Say so when you report on them. Fuel prices near a place, from Drivstoffpriser's open data. Every answer has 'say': Read 'say' aloud as it is, and never read a list. Call fuel_price with the phone's position as lat and lon, and its accuracy in metres as accuracy_m, when you have them. Without them it uses home, or asks where. If the user is or may be driving, say only the one sentence.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fuel_priceA | Find the cheapest fuel near a point; changes nothing. Names the cheapest station within about 5 km, its price, how far it is and how old the price is, in one sentence. Read 'say' aloud. |
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 1 tool
There is only one tool, so there is no possibility of misselection between overlapping tools. Its purpose (find the cheapest nearby fuel price, read-only) is unambiguous.
A single snake_case name, 'fuel_price', is clean and readable. It is a noun phrase rather than a verb_noun pattern, but with one tool there is no internal inconsistency.
The server's scope is genuinely narrow (one lookup), so a single tool is defensible, but 1 tool is on the thin side of the scale. There is no coverage for adjacent needs such as listing multiple stations or choosing fuel type.
The core read operation is covered, but notable gaps exist: no fuel-type selection (petrol/diesel/etc.), no way to return more than the single cheapest station, and no radius or sort control. These are workable but real limitations.