Skip to main content
Glama

HALOWERK EU Power Dispatch API

subscribe_price_alert

Webhook subscription for electricity price thresholds.

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_price_alert"
  }
}

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.6/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 gives only the bare fact that a webhook subscription exists. It never says that the agent's webhook_url will be called asynchronously, when or how often it fires, whether the subscription persists, or how the two threshold unit params interact — all material for a tool that reaches out to an external URL.

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

Conciseness3/5

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

A single nine-word fragment with no filler, and the core concept is front-loaded. It is efficient but so terse that it reads as a label rather than a working definition.

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?

The tool has four parameters, zero schema descriptions, and no annotations; the output schema spares it from explaining returns, but everything else is missing. For an external-callback subscription with ambiguous unit parameters, the description should do considerably more.

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 the description must compensate, yet it mentions no parameters at all. It alludes to 'thresholds' generically but never explains that threshold_g_kwh and threshold_ct_kwh are alternative unit forms, nor what the above/below direction enum means.

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 the action (a webhook subscription) and the resource (electricity price thresholds), so an agent can tell this registers a recurring alert rather than fetching prices. It does not differentiate from the sibling subscribe_co2_low, which looks structurally identical but for a different metric.

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 statement of when to choose this over subscribe_co2_low, predict_negative_price, or the plain price lookup tools, and no prerequisites or exclusions are given. The only implied usage is the generic notion of 'subscribe', leaving the agent to infer intent.

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