Skip to main content
Glama
Sign In
mcp-edf

mcp-edf

by mgcrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

EDF: Usage Breakdown

edf_get_usage_breakdown
Read-only

Estimate a home’s 12-month energy use by end use—heating, hot water, cooking, appliances, lighting—in kWh, euros, and percentages for electricity or gas; modeled from the EDF profile.

Instructions

EDF's ESTIMATE of where the energy went over the last 12 months, by use (heating, hot water, cooking, fridge and freezer, washing, lighting…), in kWh, euros and %. For electricity it adds EDF's estimate of electric heating per month as [month, kWh, €] rows. This is a model (model names EDF's algorithm) fed by the home profile declared on suiviconso.edf.fr, not a measurement: profile_declares_air_conditioning shows one profile field that changes it most. A profile that predates new equipment skews it, so update the profile on the site first. For measured figures use the consumption tools.

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": {
      "energy": "<energy>"
    },
    "name": "edf_get_usage_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
energyYesWhich meter's breakdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing that the result is an algorithmic model, not a measurement, naming the algorithm field, flagging the profile dependency and its staleness failure mode, and noting the extra monthly electric-heating rows for electricity.

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?

Front-loaded with the core definition before the caveats, and every sentence carries information. Slightly dense, with the profile_declares_air_conditioning aside bordering on implementation detail, but nothing is wasted.

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?

No output schema exists, yet the description supplies the return shape (kWh/€/% by use, plus monthly rows for electricity) and the trust level of the data. For a read-only, one-parameter tool this is complete.

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 100% for the single enum parameter, so baseline is 3, but the description adds value by explaining that the electricity branch returns additional [month, kWh, €] rows while gas does not. It stops short of further describing enum semantics, so a 4.

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 resource and scope: EDF's estimated 12-month energy breakdown by end use, in kWh, euros and percent. It contrasts itself explicitly with the measured consumption tools, so the agent can distinguish it from edf_get_electricity_consumption and edf_get_gas_consumption without opening a schema.

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 an explicit when-to-use (modelled split by use case), an explicit when-not ('For measured figures use the consumption tools'), and a prerequisite action (update the declared profile on suiviconso.edf.fr first). Nothing about selection is left to inference.

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

Deploy Server

Other Tools