Skip to main content
Glama

Fuel Prices France API: Diesel Prices, Gas Station Prices, E10

get_france_fuel_prices
Read-only

Retrieve live official fuel prices for French stations near a city, postal code or GPS point, sorted cheapest first, and compare the local price spread.

Instructions

Live official fuel prices of the stations around a French city, postal code or GPS point, cheapest first, with the local spread. Pay per result on your Apify account: run start $0.003, station $0.001.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_france_fuel_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelsNoThe first fuel drives the sorting (cheapest first).
radiusKmNoStations within this distance of each location.
locationsNoFrench cities ("Grenoble"), postal codes ("38000"), street addresses ("12 rue de la République, Lyon", measured from that exact point) or GPS points ("45.19,5.72").
maxStationsPerLocationNoCheapest first (by the first fuel). Default here: 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / locations / description
      Previous value: -"French cities (\"Grenoble\"), postal codes (\"38000\") or GPS points (\"45.19,5.72\")."New value: +"French cities (\"Grenoble\"), postal codes (\"38000\"), street addresses (\"12 rue de la République, Lyon\", measured from that exact point) or GPS points (\"45.19,5.72\")."
  2. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful cost details: run start $0.003 and $0.001 per station. It also discloses sorting behavior and 'local spread,' though it does not cover authentication or rate-limit behavior.

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?

Two sentences are front-loaded with the core purpose, followed by pricing information. There is no redundant or wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read-only tool with no output schema, the description covers the key inputs, sorting behavior, and per-result cost. It could say more about the exact return shape, but it is sufficient for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the fuels, radius, locations, and station-limit parameters. The description reinforces location types and cheapest-first sorting but adds little semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: live official fuel prices for stations around a French city, postal code, or GPS point, sorted cheapest first. It is clear what the tool returns, though it does not explicitly differentiate itself from any named sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it by specifying French locations and fuel-price retrieval, but it gives no explicit when-not guidance or alternatives. The use case is clear from context, but routing guidance is absent.

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