Skip to main content
Glama

HALOWERK EU Power Dispatch API

buy_market_brief

Returns licensed ENTSO-E and SMARD spot-market context for compute, DePIN, battery and power-trading agents: published day-ahead prices, volatility, load, renewable share when available, the observed share of published negative-price hours, uncertainty, freshness and expiry.

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": {
      "region": "<region>",
      "horizon_hours": "<horizon_hours>",
      "use_case": "<use_case>"
    },
    "name": "buy_market_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYes
use_caseYes
horizon_hoursYes

Output Schema

NameRequiredDescriptionDefault
loadYes
expires_atYes
volatilityYes
spot_marketYes
uncertaintyYes
model_versionYes
price_forecastYes
payment_receiptYes
renewable_shareYes
source_timestampsYes
source_attributionsYes
negative_price_probabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 real behavioral traits: licensed/proprietary provenance (ENTSO-E, SMARD), variable availability ('when available'), and explicit uncertainty, freshness and expiry outputs. It stops short of stating auth/entitlement requirements or rate limits, but the licensing and freshness disclosures are meaningful context beyond a bare summary.

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 dense sentence, front-loaded with the core verb and data source, then listing the metrics. The metric list is long but each item is informative; no filler or repetition.

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?

The tool has an output schema, so the description need not explain return values, and its licensing/availability notes cover the missing annotations reasonably well. However, for a three-parameter tool with zero schema coverage, leaving region format and horizon semantics unexplained is a real gap for correct invocation.

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

Parameters2/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. It only implicitly maps the four use_case enum values to the audience list; region (expected format like 'DE-LU') and horizon_hours (1-48 range, what the horizon governs) are not explained at all, leaving two of three parameters undocumented in both schema and prose.

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 opens with a specific verb and resource ('Returns licensed ENTSO-E and SMARD spot-market context') and enumerates the exact metrics returned. It is clear what the tool does, but it does not differentiate itself from metric-specific siblings such as price_spot, renewable_share or grid_load, so an agent cannot tell from the text alone when this bundle beats those.

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?

The audience framing ('for compute, DePIN, battery and power-trading agents') implies usage and maps loosely to the use_case enum, but there is no explicit when-to-use vs when-not guidance and no named alternative for narrower queries. Usage is implied rather than stated.

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