Skip to main content
Glama

HALOWERK EU Power Dispatch API

subscribe_co2_low

Returns a webhook subscription that notifies your URL when the CO2 intensity of the German electricity mix falls below your threshold.

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": {
      "webhook_url": "<webhook_url>"
    },
    "name": "subscribe_co2_low"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionNo
webhook_urlYes
threshold_g_kwhNo
threshold_ct_kwhNo

Output Schema

NameRequiredDescriptionDefault
successYes
subscriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 behavioral burden and does not meet it. It implies a push-notification flow but says nothing about persistence, notification cadence, delivery failure handling, or webhook verification, which are exactly the traits an agent needs before creating a subscription.

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?

A single efficient sentence with the trigger condition front-loaded and no filler. It is short to a fault, but nothing in it is wasted.

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?

An output schema exists, so return values need not be explained, but for a 4-parameter mutation-like subscription tool with zero schema coverage and no annotations the definition is too thin. The unit ambiguity between the two threshold parameters and the above/below direction are unresolved gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so four parameters are undocumented structurally, and the description only gestures at "your threshold" and "your URL". It never explains why there are two separate thresholds (threshold_g_kwh vs threshold_ct_kwh, apparently different units) or how the direction enum interacts with the stated "falls below" behavior.

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+resource ("Returns a webhook subscription") and scope (CO2 intensity of the German electricity mix crossing a threshold), which is far clearer than the name alone. It does not distinguish itself from subscribe_price_alert, and it only mentions the "below" case even though the schema exposes a direction enum of above/below.

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 guidance on when to pick this over subscribe_price_alert or carbon_now, and no prerequisites such as whether webhook_url must be pre-verified, whether the subscription persists, or how it is later cancelled. The agent must infer all selection and setup behavior.

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