Skip to main content
Glama

Get fuel prices

well_get_fuel_prices
Read-only

Find the cheapest stations for one fuel around a point in France, from the national fuel price open data (prices that stations report, refreshed through the day). Use it when the person asks where to fill up or what fuel costs near a place. It covers France only. Get the point from well_get_address_location first when the person gave an address.

Pass latitude, longitude, fuel (gazole, e10, sp98, sp95, e85, gplc) and, optionally, radius_km (default 5, at most 20) and limit (default 5, at most 10).

Returns status "found" with stations, cheapest first, each with address, postal_code, city, its point, price_eur_per_litre, price_updated_at (a price a few days old may have changed: say when it is) and open_24h (null: unknown). Or status "refused" with refusal: "not_found" (no station with that fuel in the radius), "unavailable" or "malformed_input"; pass on message and never invent a price.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "fuel": "<fuel>"
    },
    "name": "well_get_fuel_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelYesThe fuel.
limitNo
latitudeYesLatitude of the centre point.
longitudeYesLongitude of the centre point.
radius_kmNo
workspace_idNoTarget workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
fuelNo
sourceNo
statusYes
messageNo
refusalNo
successYes
stationsNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / source / enum
      Previous value: -[
      -  "fr_recherche_entreprises",
      -  "gb_companies_house",
      -  "us_sec_edgar",
      -  "eu_vies",
      -  "gb_hmrc",
      -  "fr_base_adresse_nationale",
      -  "us_census_geocoder",
      -  "nager_public_holidays",
      -  "fr_prix_des_carburants",
      -  "navitia_journeys"
      -]New value: +[
      +  "fr_recherche_entreprises",
      +  "gb_companies_house",
      +  "us_sec_edgar",
      +  "eu_vies",
      +  "gb_hmrc",
      +  "fr_base_adresse_nationale",
      +  "us_census_geocoder",
      +  "nager_public_holidays",
      +  "fr_prix_des_carburants",
      +  "navitia_journeys",
      +  "youtube_oembed",
      +  "fr_bodacc"
      +]
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description still adds real operational context: prices are station-reported and refreshed through the day, a stale price may have changed and should be flagged, and open_24h can be null (unknown). It also discloses the full outcome contract (status found vs. refused with not_found / unavailable / malformed_input) and the instruction never to invent a price.

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?

Three short blocks — purpose/scope, inputs, outputs — with the routing intent and the geocoding prerequisite front-loaded. Every sentence carries distinct information (scope, defaults, staleness warning, refusal handling); nothing is repeated from the name or annotations.

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?

For a read-only lookup with eight parameters, the definition covers what an agent needs: when to call it, the prerequisite for producing coordinates, geographic limits, parameter defaults and bounds, and every return branch including error refusal codes. Return-value detail beyond this is handled by the existing output schema, so nothing material 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 75%, and the description still adds value the schema lacks: the enumerable fuel codes are listed in prose and, importantly, the defaults for radius_km (5, max 20) and limit (5, max 10), which appear only as bounds in the schema. It says nothing about the workspace/conversation parameters, but those carry their own schema descriptions.

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 ("Find the cheapest stations for one fuel around a point") plus the data source (national fuel price open data) and an explicit geographic scope (France only). This is far more than a restatement of the name and lets an agent distinguish it from generic search or address tools.

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?

Gives the triggering user intent ("where to fill up or what fuel costs near a place"), an explicit boundary (France only), and a prerequisite chain ("Get the point from well_get_address_location first when the person gave an address"). It names a concrete alternative for the geocoding sub-task rather than leaving it to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources