Skip to main content
Glama

HALOWERK EU Power Dispatch API

carbon_now

Current CO2 intensity of the German electricity mix.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
classificationYes
carbon_intensity_g_co2_kwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about units (e.g. gCO2eq/kWh), update frequency/latency, data source, or geographic caveats such as whether cross-border flows are included. The operation is inherently read-only, which limits the risk, but the missing unit and freshness context materially affect interpretation.

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 sentence with no filler, and the most important qualifier (current) is placed prominently. Nothing could be removed without losing meaning.

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

Completeness4/5

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

For a no-parameter read of a single metric with an output schema already defining the return shape, the description covers the essentials: what is measured and for which grid. Only the measurement unit and refresh cadence are absent, which are minor given the output schema exists.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly signals that no inputs are needed by framing the result as a single current value.

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 a specific resource (CO2 intensity), a specific geographic scope (German electricity mix), and a temporal scope (current), which is enough to distinguish it from siblings such as renewable_share, grid_load, or history_prices. It is a noun phrase rather than a verb+resource statement, but for a zero-parameter getter the intent is unambiguous.

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 guidance, no prerequisites, and no pointer to related siblings such as subscribe_co2_low (for alerts when intensity drops) or renewable_share (a related metric). The agent must infer from the name alone whether to poll this or use a subscription-style tool.

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