Skip to main content
Glama

HALOWERK EU Power Dispatch API

buy_dispatch_plan

Schedules a deadline-bound compute, DePIN, battery or power-trading workload into an actionable German or European power window. Returns exact timing, expected EUR cost and savings, uncertainty, freshness, expiry and decision trace.

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": {
      "opportunity_id": "<opportunity_id>",
      "power_kw": "<power_kw>",
      "energy_kwh": "<energy_kwh>",
      "deadline": "<deadline>",
      "risk_profile": "<risk_profile>"
    },
    "name": "buy_dispatch_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
deadlineYes
power_kwYes
energy_kwhYes
constraintsNo
risk_profileYes
opportunity_idYes

Output Schema

NameRequiredDescriptionDefault
actionYes
confidenceYes
expires_atYes
risk_flagsYes
uncertaintyYes
schedule_endYes
model_versionYes
decision_traceYes
schedule_startYes
payment_receiptYes
baseline_cost_eurYes
expected_cost_eurYes
source_timestampsYes
source_attributionYes
expected_savings_eurYes
expected_carbon_effectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 burden; it does add real behavioral context by saying results carry uncertainty, freshness and expiry, implying the plan is time-limited and probabilistic rather than a guarantee. However, despite the 'buy_' prefix it never states whether calling this commits money/reserves capacity, whether the operation is idempotent or reversible, or what permissions it requires.

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?

Two tight sentences with the action front-loaded and the return contents enumerated compactly; nearly every clause earns its place. Minor jargon density ('DePIN', 'decision trace') without gloss, but no padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex optimization/pricing tool with five required parameters, a nested constraints object and zero annotation coverage, yet the description omits parameter meaning, prerequisite sourcing for opportunity_id, and side-effect profile. The existence of an output schema excuses it from detailing return values, but the invocation-side gaps remain substantial.

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

Parameters1/5

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

Schema description coverage is 0% across six parameters, including a nested constraints object with four sub-fields and a risk_profile enum, and the description explains none of them. It gives no meaning for opportunity_id, power_kw vs energy_kwh, or what conservative/balanced/aggressive actually change, so it fails to compensate for the schema gap.

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?

States a specific verb (schedules) and a specific resource/outcome (a deadline-bound workload into an actionable German/European power window), plus the workload types it supports. It is clearly distinct from read-only siblings like price_spot or grid_load, though it never names a sibling such as flexibility_window or optimizer_cheapest_window to draw the boundary.

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 when-to-use/when-not guidance, no mention of how or where opportunity_id is obtained, and no statement of prerequisites or alternatives among the many window/price siblings. Usage is only inferable from the phrase 'Schedules a deadline-bound ... workload.'

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