Skip to main content
Glama

toll402 – EU & Nordic Data (x402)

dk_power_cheapest_window

Cheapest contiguous window of N hours to run a load (EV charging, heat pump, batch job) on a given day in Denmark (DK1/DK2), Norway NO2, Sweden SE3/SE4 or Germany DE-LU, based on day-ahead spot prices. Source: Energinet, energidataservice.dk (CC BY 4.0). Price 0.005 USD per call via x402.

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>"
    },
    "name": "dk_power_cheapest_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYesBidding zone: DK1, DK2, NO2, SE3, SE4 or DE (DE-LU)
dateNodate
hoursNoWindow length in hours (1-12)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"area"New value: +"Bidding zone: DK1, DK2, NO2, SE3, SE4 or DE (DE-LU)"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose two non-obvious behaviors: the upstream data source/license (Energinet, CC BY 4.0) and a per-call cost of 0.005 USD via x402. What it omits is the response shape (does it return a start time, the average price, savings vs. baseline?) and behavior on invalid areas or out-of-range hours.

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?

The core capability is front-loaded in a single dense sentence, with source and cost appended as compact metadata. Nothing is wasted, though the source attribution is slightly redundant with the URL and could be trimmed.

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

Completeness3/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 explain the return value, and it does not — an agent cannot tell whether it receives a time range, a price, or a comparison to a flat-rate baseline. Source and pricing context are covered, but the missing return contract is a real gap for a decision-support tool.

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 area, date and hours are already documented in the schema, including the 1-12 range. The description reinforces that the window is contiguous and that pricing is day-ahead, but adds no format or edge-case detail (e.g., timezone of 'date', behavior when hours exceeds the day's remaining slots). Baseline 3 applies.

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 operation: finding the cheapest contiguous N-hour window based on day-ahead spot prices, scoped to named bidding zones. It is clearly distinct from a raw price lookup like dk_power_price, though it never names that sibling explicitly. Verb + resource + scope are all present.

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?

Concrete load examples (EV charging, heat pump, batch job) imply when the tool is appropriate, which is better than nothing. However, there is no explicit guidance on when to use dk_power_price instead, no mention of the same-day/next-day availability window for day-ahead prices, and no stated exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.