Skip to main content
Glama
energidata-mcp

energidata-mcp

by batutho-dot

best_hours

Identify the lowest-CO2 or cheapest hours in a Danish electricity window to schedule heat pumps, EV charging, or other flexible loads, with optional consecutive-hour blocks.

Instructions

Find the cleanest (lowest CO2) or cheapest hours in a window, e.g. when to run a heat pump or charge a car.

metric: 'co2' or 'price'. n_hours: how many hours to pick. consecutive=True returns the block of n back-to-back hours with the lowest mean instead of the n lowest single hours. highest=True flips it to the dirtiest / most expensive hours. Times are Danish local time.

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": {
      "area": "<area>",
      "metric": "<metric>",
      "start": "<start>"
    },
    "name": "best_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
areaYes
startYes
metricYes
highestNo
n_hoursNo
currencyNoDKK
co2_sourceNoauto
consecutiveNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose non-obvious behavior such as consecutive block selection by mean, the highest flip, and that times are Danish local time. It omits how co2_source 'auto' falls back, what happens when the window is shorter than n_hours, date format expectations, and currency conversion behavior.

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 purpose sentence followed by compact parameter notes; nearly every sentence earns its place. Slight loss for packing several parameters into a dense paragraph without structure, but the text is tight overall.

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

Completeness2/5

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

For a 9-parameter tool with zero schema coverage and no annotations, the definition does too little: date/time format for the required start and end, area semantics, currency handling, and co2_source fallback are all left to guesswork. The output schema existing removes the need to describe return values, but the input side remains thin.

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 0%, so the description must compensate, and it does clarify four knobs (metric, n_hours, consecutive, highest) whose meaning is not obvious from their names. However, five parameters — including the required 'start'/'end' format, 'currency', and the three-way 'co2_source' — receive no explanation at all.

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?

States a specific verb and resource: find the cleanest/cheapest hours in a time window, with a concrete use case (heat pump, EV charging). It is clearly distinguishable from siblings co2_intensity and spot_price, which imply raw series reads, though the description never names them explicitly.

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?

The opening sentence and examples give clear context for when to reach for this tool (optimizing an energy-consuming action), and the metric note implies choosing co2 vs price. There are no explicit exclusions or pointers to the sibling tools for raw data retrieval.

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