Current grid electricity carbon intensity for a zone in gCO2/kWh. Lower values mean cleaner power — use for carbon-aware workload routing or comparing cleanliness across times or regions.
| Name | Required | Description | Default |
|---|---|---|---|
| zone | Yes | Bidding zone code (e.g. DE, FR, SE, NO). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the data is 'current', provides units (gCO2/kWh), and adds interpretive value ('Lower values mean cleaner power'). This goes beyond the basic purpose to explain behavior and meaning.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main purpose, and every sentence provides actionable information without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description fully covers what the tool returns, its units, and its intended use cases. It is complete enough for an agent to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with the zone parameter described as 'Bidding zone code (e.g. DE, FR, SE, NO)'. The description itself does not add parameter-level detail beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the current grid electricity carbon intensity for a specific zone in gCO2/kWh, which is a specific verb+resource+scope. It distinguishes from siblings by emphasizing 'for a zone', which contrasts with tools like get_global_carbon.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly mentions use cases: 'use for carbon-aware workload routing or comparing cleanliness across times or regions.' It provides clear context for when to use this tool, though it does not explicitly name alternatives or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.