fuel-map-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPINET_API_KEY | Yes | Your Opinet API key | |
| KAKAO_REST_API_KEY | Yes | Your Kakao REST API key |
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 |
|---|---|
| get_routeA | Retrieves route information between origin and destination using Fuel Station Compass(주유소 나침반). This tool queries Kakao Mobility API to get detailed route information including distance, duration, tolls, and route coordinates. Args: origin: Starting location address or place name (e.g., "Gangnam Station", "Seoul Gangnam-gu Teheran-ro 212") destination: Destination address or place name (e.g., "Pangyo Station") priority: Route priority - RECOMMEND | TIME | DISTANCE (default: RECOMMEND) Returns: distance_km: Total distance in kilometers (1 decimal place) duration_min: Estimated travel time in minutes toll_fare: Toll fees in KRW taxi_fare: Estimated taxi fare in KRW origin: Origin location name and coordinates destination: Destination location name and coordinates |
| find_cheapest_gas_stations_nearbyA | Finds the 5 cheapest gas stations near a specific location using Fuel Station Compass(주유소 나침반). This tool searches for gas stations within the specified radius using Opinet API and returns the top 5 cheapest options sorted by price. Args: location: Location address or place name (e.g., "Gangnam Station", "Seoul Gangnam-gu Teheran-ro 212") fuel_type: Fuel type code - B027: Gasoline(default), D047: Diesel, K015: Kerosene, C004: LPG radius: Search radius in meters (max 5000, default: 1000) Returns: location: Search location name gas_stations: Top 5 cheapest gas stations [ { "name": Station name, "brand": Brand name, "price": Price in KRW, "distance": Distance from location in meters }, ... ] |
| find_cheapest_gas_stations_on_routeA | Finds the 5 cheapest gas stations along a route using Fuel Station Compass(주유소 나침반). Samples the route and searches for gas stations within 1km radius at each point, returning the top 5 cheapest options. Args: origin: Starting location (e.g., "Gangnam Station") destination: Destination (e.g., "Pangyo Station") fuel_type: B027(Gasoline), D047(Diesel), K015(Kerosene), C004(LPG) priority: RECOMMEND | TIME | DISTANCE (default: RECOMMEND) Returns: route_info: Route details (distance_km, duration_min, origin/destination names) gas_stations: Top 5 cheapest stations with name, brand, price, distance |
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 3 tools
The three tools have distinct purposes: route retrieval, station search near a point, and station search along a route. The two station-finding tools could be momentarily confused, but the 'nearby' vs 'on_route' naming and the differing required arguments (location vs origin/destination) clearly delineate them.
Naming is mixed: 'get_route' uses a verb_noun pattern, while the other two are long descriptive phrases starting with 'find_'. The inconsistency is readable but breaks a predictable convention.
Three tools is borderline thin for a fuel-mapping service. It covers core needs, but adding tools like price alerts or station details would likely be expected.
The surface covers route retrieval and finding cheap stations both nearby and along a route. Missing are operations like getting station details, user preferences, or fuel price trends, but the core workflow is complete.