Skip to main content
Glama

HALOWERK EU Power Dispatch API

predict_negative_price

Battery, EV, and trading agents buy this endpoint to receive calibrated 2h/4h/6h negative-price probabilities, reviewed threshold profiles and an executable response policy.

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

Input Schema

NameRequiredDescriptionDefault
policy_profileNoSelects the reviewed probability threshold profile without changing the underlying calibrated probabilities.balanced

Output Schema

NameRequiredDescriptionDefault
okYes
resultYes
endpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It implies the operation is a computation/read ('receive ... probabilities') and names the artifacts returned, but says nothing about cost, latency, caching, whether values are deterministic, or what 'executable response policy' actually means in practice. The marketing tone substitutes for behavioral detail rather than supplying it.

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

Conciseness3/5

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

It is a single sentence, which is appropriately sized, but the leading clause about who buys the endpoint is promotional filler that does not help an agent decide or call. The useful content (horizons, calibrated probabilities, policy) is buried mid-sentence rather than front-loaded.

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 is low complexity — one optional enum parameter and an output schema that documents the return shape — so the description need not explain values. However, it leaves two real gaps: no routing guidance against the near-identical sibling price_negative_forecast, and it advertises 2h/4h/6h horizons that no parameter exposes, which could mislead an agent into searching for a horizon argument that does not exist.

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 coverage is 100% and the single enum parameter is fully documented in the schema, including that it changes the threshold profile but not the underlying probabilities. The description's mention of 'reviewed threshold profiles' loosely echoes policy_profile but adds no new semantics such as how to choose among balanced/utility/precision/recall. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence names a concrete resource — calibrated 2h/4h/6h negative-price probabilities plus a threshold profile and response policy — which is more than a restatement of the name. But the action verb is only implicit ('receive'), and the framing 'agents buy this endpoint' is promotional rather than functional. It also gives no hint of how it differs from the sibling price_negative_forecast, which appears to cover adjacent ground.

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?

The only usage signal is an audience label ('Battery, EV, and trading agents'), which names who might be interested rather than when to call this versus an alternative. There is no when-to-use, no when-not-to-use, and no mention of price_negative_forecast or price_forecast despite obvious overlap.

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