mcp-edf

EDF: Gas Consumption

edf_get_gas_consumption

Read-only

Retrieves daily or monthly gas consumption in kWh, m³, and euros from the Gazpar meter via EDF Suivi Conso for a date range, with totals for the period.

Instructions

Gas used per day or per month from the Gazpar meter via EDF Suivi Conso: kWh, m³, the conversion factor between them, and euros (energy plus the daily share of the subscription). total sums the range. Costs are EDF's estimate at the contract's prices, taxes included. Daily figures need a communicating Gazpar meter and arrive a day or two late; months are available further back. Answers 404 on an account with no gas contract.

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": {
      "from": "<from>"
    },
    "name": "edf_get_gas_consumption"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	Last day, INCLUSIVE, as YYYY-MM-DD, e.g. 2026-10-31. Defaults to yesterday: the meters report once a day, and a day's figures usually land the next morning around 08:00.
`from`	Yes	First day, inclusive, as YYYY-MM-DD in Paris time, e.g. 2026-10-01.
`step`	No	day: one row per day (at most 400 days). month: one row per calendar month.	day

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnly and openWorld, so the description carries the rest and does it well: costs are EDF estimates at contract prices with taxes included, `total` sums the range, daily figures are delayed and meter-dependent, and the 404 failure mode is spelled out. That is exactly the context an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, each carrying distinct information, with the core purpose front-loaded. The opening sentence is long and packs return fields, granularity, and source together, but nothing is redundant.

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?

There is no output schema, so the description correctly takes on the job of describing return fields and the `total` aggregate. Combined with prerequisites, latency, and error behavior, an agent has everything needed to call this 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 coverage is 100%, so from/to/step semantics, defaults, and the 400-day cap are already documented in the schema. The description adds only a light gloss ('per day or per month') and otherwise defers to the schema, which is the expected baseline.

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 — gas used per day or per month from the Gazpar meter via EDF Suivi Conso — and enumerates the returned measures (kWh, m³, conversion factor, euros). The gas framing cleanly separates it from the electricity consumption sibling without needing to name it.

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

Usage Guidelines4/5

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

Gives real preconditions: daily granularity requires a communicating Gazpar meter, daily data arrives a day or two late while months go further back, and a no-gas-contract account returns 404. It stops short of naming an alternative tool or an explicit when-not-to-call rule.

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

Deploy Server