Skip to main content
Glama

HALOWERK EU Power Dispatch API

history_prices_stats

Returns statistics (minimum, maximum, mean and distribution) of German day-ahead electricity prices for one historical period.

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": {
      "period": "<period>"
    },
    "name": "history_prices_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYes

Output Schema

NameRequiredDescriptionDefault
avg_eur_mwhYes
max_eur_mwhYes
min_eur_mwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and does not say whether data covers the full available history, how far back the archive goes, what timezone/currency the prices are in, or how the distribution is presented. It is clearly a read-style statistics query so risk is low, but no operational context is disclosed beyond the returned metrics.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; every clause (metrics, domain, scope) 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?

An output schema exists, so return-value detail need not be restated, and the single required parameter is constrained by a regex with examples. The remaining gap is routing information: nothing tells the agent when to pick this over history_prices or price_forecast.

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?

The phrase 'for one historical period' adds real meaning: the agent learns only a single period is accepted, not a start/end pair, which heads off a plausible misuse. The remaining syntax burden falls on the schema's regex and examples (last-7d, 2025-Q4, 2024-01), which at 0% description coverage still leave the description doing only partial work.

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 gives a specific verb (returns statistics) and enumerates the exact measures (minimum, maximum, mean and distribution) for a named resource (German day-ahead electricity prices). That output enumeration implicitly separates it from sibling history_prices, which presumably returns the raw series, though the sibling is never named explicitly.

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?

Usage is only implied: 'statistics' and 'one historical period' suggest this tool when an aggregate is wanted rather than a per-hour series, but there is no explicit when-to-use, when-not-to-use, or named alternative such as history_prices or price_forecast.

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.

Resources