Skip to main content
Glama

HALOWERK EU Power Dispatch API

price_forecast

Energy-trading and flexible-load agents buy this endpoint to compare the next 24 hours of EPEX prices and volatility.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
hoursYes
hourlyYes
sourceYes
timestampYes
stats_eur_mwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 discloses the data returned (prices and volatility over the next 24 hours), but does not mention whether the operation is read-only (though implied), rate limits, authentication needs, or other operational traits beyond what the output schema likely covers.

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 description is a single, front-loaded sentence that conveys the core purpose without unnecessary wording. The phrase 'buy this endpoint' adds slight marketing flavor but does not detract significantly from clarity.

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?

Given the tool's simplicity (no parameters) and the presence of an output schema, the description provides enough context: it specifies the forecast horizon, data type (EPEX prices and volatility), and target users. A minor gap is the lack of distinction from similar forecast tools, but overall it is complete for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description adds no parameter information, but none is needed, and the schema coverage is 100% (though empty).

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 verb ('compare') and resource ('next 24 hours of EPEX prices and volatility'), making the tool's function clear. However, it does not differentiate itself from siblings like price_spot or price_negative_forecast, so an agent cannot distinguish its niche without further inference.

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?

It implies usage for energy-trading and flexible-load agents, giving a target audience and general context. But it offers no explicit when-to-use or when-not-to-use guidance relative to alternatives such as history_prices or price_spot, leaving selection ambiguous.

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