Skip to main content
Glama

HALOWERK EU Power Dispatch API

energy_decision

EV, battery, and flexible-load agents buy this endpoint to receive an executable action with timing, expected value, confidence, and expiry.

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

Input Schema

NameRequiredDescriptionDefault
goalNobalanced
deviceNogeneric
deadlineNo
locationNoGermany
constraintsNo
duration_hoursNo
policy_profileNoOptional override. Trading defaults to precision; flexible devices default to utility.

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 must carry the full behavioral burden. It discloses the returned decision components (timing, expected value, confidence, expiry), but it never states whether the endpoint only computes a recommendation or also executes/schedules actions, nor does it mention cost, permissions, rate limits, or idempotency.

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?

It is a single front-loaded sentence with no redundant clauses. The only weakness is the somewhat promotional 'buy this endpoint' phrasing, which is less precise than a plain statement of what the tool returns.

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?

For a seven-parameter tool with a nested constraints object, zero required parameters, no annotations, and only 14% schema description coverage, the definition leaves too much unexplained. Although an output schema exists—so return fields need not be detailed—the description still does not explain parameter behavior or operational constraints.

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 only 14%, and the description adds no information about the seven inputs: goal, device, deadline, location, constraints (with min_soc/target_soc/etc.), duration_hours, or policy_profile. The schema's enums and defaults are the only semantic aid.

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 sentence identifies the audience (EV, battery, flexible-load agents) and the product returned—an executable action with timing, expected value, confidence, and expiry—so an agent can tell it produces an actionable recommendation rather than raw market data. It does not explicitly differentiate itself from sibling decision or dispatch tools, and the marketplace phrasing 'buy this endpoint' slightly obscures the operation.

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?

No when-to-use or when-not-to-use guidance is given beyond the audience note, and no alternatives or preconditions are mentioned. An agent must infer that this is for device agents seeking an action, but nothing says how it compares with other planning or trading endpoints.

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