Skip to main content
Glama

HALOWERK EU Power Dispatch API

signals_buy_sell

Energy price indicators for German day-ahead electricity prices: position of the current hour in the 24-hour range (RSI-style, 0-100), Z-score against the 7-day average, trend between the first and second 12 hours in ct/kWh, renewable pressure and fossil share, summed into a composite score with a descriptive relative-price label. Descriptive market statistics only, no trading recommendation and no investment advice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noticeYes
sourceYes
factorsYes
timestampYes
indicatorsYes
market_dataYes
methodologyYes
valid_untilYes
composite_labelYes
composite_scoreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden and does well: it discloses the computations, the units (ct/kWh), the normalization window (0-100, 7-day lookback), and explicitly bounds the tool's claims ('no trading recommendation and no investment advice'). It does not state data freshness/update cadence or whether the current hour value is live or lagged, which is the main remaining gap.

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 metric inventory is front-loaded and each clause earns its place by mapping to a distinct returned field. The trailing disclaimer is slightly repetitive ('no trading recommendation and no investment advice') but is justified given the buy/sell naming.

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?

Since an output schema exists, return values needn't be explained, and the description appropriately focuses on what is computed and its limits. However, for a no-input, real-time market signal tool, the missing pieces are update cadence, the market/time-frame it reflects, and how the composite score maps to its label — details an agent would need to use the values responsibly.

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 takes zero parameters, so the baseline is 4; the description correctly adds no parameter guidance because none is needed. It does clarify that outputs are derived for the current hour implicitly, giving context on what is being measured.

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 concrete resource (German day-ahead electricity price indicators) and enumerates the specific derived metrics it returns — RSI-style hour position, Z-score vs 7-day average, 12h/12h trend, renewable pressure, fossil share, composite score. This also usefully corrects the potentially misleading 'buy_sell' name by stating the tool is descriptive statistics only. It does not explicitly contrast itself with derived-stat siblings such as history_prices_stats or energy_decision, so it stops short of 5.

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: an agent can infer the tool is for obtaining current-hour normalized/derived price indicators rather than raw prices, and the disclaimer signals it should not be used as a trading recommendation. There is no explicit when-to-use or when-to-prefer-an-alternative statement naming siblings like price_spot or energy_decision.

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