Skip to main content
Glama

HALOWERK EU Power Dispatch API

region

Returns electricity price, CO2 intensity, renewable share and weather for one German postal code region.

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": {
      "plz": "<plz>"
    },
    "name": "region"
  }
}

Input Schema

NameRequiredDescriptionDefault
plzYes

Output Schema

NameRequiredDescriptionDefault
plzYes
dataYes
regionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden but only lists returned fields. It does not state whether values are live/current, forecast, or historical, nor anything about freshness, latency, rate limits, or behavior for an unknown postal code — for a data-fetch tool, temporal semantics are the crucial missing trait.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; every clause (fields returned, region scope, country) carries information.

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?

Complexity is low and an output schema exists, so return values need no explanation here. Still, for a data tool the description omits temporal/freshness semantics and error behavior for invalid or uncovered postal codes, which an agent needs to use it correctly.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it tells the agent the parameter is a German postal code and that exactly one region is queried per call, adding country and cardinality meaning beyond the bare ^[0-9]{5}$ pattern.

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 ('Returns') and an explicit bundle of resources — electricity price, CO2 intensity, renewable share, weather — scoped to one German postal code region. That composite/regional scope distinguishes it from single-signal siblings such as carbon_now, renewable_share or price_spot, though no sibling is named.

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 this is the one-call regional snapshot tool, but the description never says when to prefer it over carbon_now, renewable_share or price_spot, nor any prerequisite or exclusion.

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