Skip to main content
Glama

HALOWERK EU Power Dispatch API

history_prices

Returns hourly EPEX day-ahead electricity prices for Germany for one 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYes

Output Schema

NameRequiredDescriptionDefault
rowsYes
periodYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the data source (EPEX day-ahead), the hourly granularity, and the covered region, which is useful, but says nothing about units, currency, timezone, or handling of unavailable or partial periods.

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?

A single front-loaded sentence with no filler; the resource and granularity lead. It is efficient, though the brevity leaves the gaps noted in other dimensions.

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?

An output schema exists, so return structure need not be explained, and there is only one parameter. Still, for a domain-data tool an agent needs to know units (EUR/MWh), timezone conventions, and whether the current incomplete period is included; none of that appears.

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%, but the schema itself supplies a tight regex pattern plus examples (last-7d, 2025-Q4, 2024-01), so acceptable formats are already evident. The description adds only the vague phrase 'one period' and does not explain relative-versus-calendar semantics or how quarter/month ranges resolve to hourly rows.

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 names a specific verb and resource: hourly EPEX day-ahead electricity prices for Germany over one period. It is concrete about market, granularity, geography, and scope, but never distinguishes itself from close siblings such as history_prices_stats, price_spot, or price_forecast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this tool over the related siblings (history_prices_stats for aggregates, price_spot for current price, price_forecast for future values). The only hint is the phrase 'for one period', which implies a single contiguous range but states no 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.

Resources