Skip to main content
Glama
Sign In
mcp-edf

mcp-edf

by mgcrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

EDF: Electricity Max Power

edf_get_electricity_max_power
Read-only

Retrieve daily maximum power in kVA over a date range and compare the peak with subscribed power to decide whether the electricity contract level is too high or near tripping.

Instructions

The highest power drawn each day, in kVA, as [date, max_kva] rows, with the range maximum and the subscribed power of the current contract to compare against. Use it to decide whether the subscription (e.g. 6, 9, 12 kVA) is too high or close to tripping. The meter's history goes back years; this filters it to the range asked.

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": "edf_get_electricity_max_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast 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.
fromNoFirst day, inclusive, YYYY-MM-DD. Defaults to 30 days before `to`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral facts — reporting cadence of once per day, data landing the next morning around 08:00, and the fact that history extends back years. It also discloses the comparison values bundled into the response (range maximum, subscribed power), which is behavior the annotations cannot express. It does not discuss failure modes for out-of-range dates or empty intervals.

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?

Three sentences, front-loaded with the return shape before the purpose, then the data-availability caveat. No filler or repetition of the title. The middle clause about range maximum and subscribed power is dense but each element carries information.

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?

There is no output schema, so the description must describe the return shape, and it does: [date, max_kva] rows plus the range maximum and current subscribed power, with units in kVA. Combined with the schema's date defaults, an agent has enough to call this correctly. Minor gaps remain around empty ranges or meter unavailability.

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%, with both `from` and `to` fully documented including inclusive semantics and defaults, so the schema does the heavy lifting. The description reinforces why the default window matters (daily reporting cadence, next-morning arrival) but adds no new syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 resource and metric: the daily maximum power drawn in kVA, returned as [date, max_kva] rows alongside the range maximum and the subscribed power. That is far more precise than the title alone and lets an agent infer the distinction from load-curve or consumption siblings. It stops short of naming the sibling it differs from (e.g. edf_get_electricity_load_curve), so it is clear but not explicitly differentiated.

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?

It gives an explicit decision context: 'Use it to decide whether the subscription (e.g. 6, 9, 12 kVA) is too high or close to tripping,' which tells the agent what question this tool answers. It also clarifies that the source history spans years and that the date range narrows it, implying the range should be chosen deliberately. There are no explicit exclusions or named alternative tools, which keeps it below a 5.

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