Skip to main content
Glama
energidata-mcp

energidata-mcp

by batutho-dot

co2_intensity

Retrieve hourly CO2 intensity in g CO2/kWh for Danish price areas DK1 and DK2 over a chosen time range, using measured or forecast data to assess electricity emissions.

Instructions

CO2 intensity of electricity consumed in a Danish price area, per hour, in g CO2 per kWh.

start/end: Danish local time, '2026-11-17' or '2026-11-17T06:00'; end is exclusive and defaults to the next midnight. source: 'measured' (CO2Emis), 'forecast' (CO2EmisProg), or 'auto' = measured when the window is in the past, otherwise forecast. Each hour is the mean of the 5-minute values in it; 'samples' says how many there were (12 = complete).

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": {
      "area": "<area>",
      "start": "<start>"
    },
    "name": "co2_intensity"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
areaYes
startYes
sourceNoauto

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the exclusive end boundary with its default (next midnight), the aggregation rule (mean of 5-minute values per hour), and the 'samples' completeness indicator (12 = complete). It omits latency, error behavior, and data availability limits, keeping it short of a 5.

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?

Front-loaded with the core purpose, then per-parameter semantics and finally the aggregation note; every sentence carries information. The line-broken layout is slightly dense but no sentence is wasted.

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?

An output schema exists, so return structure needn't be explained, yet the description still clarifies the 'samples' field usefully. For a 4-parameter read tool the coverage is nearly complete; only cross-tool routing guidance versus siblings is missing.

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 largely does: start/end accept date or datetime forms in Danish local time, end is exclusive with a documented default, and the source enum is fully explained value by value. The area parameter is only implied by 'Danish price area' rather than described, which is the one gap.

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 resource and measurement precisely: 'CO2 intensity of electricity consumed in a Danish price area, per hour, in g CO2 per kWh', including granularity and unit. It does not distinguish itself from siblings spot_price or best_hours, so the agent must infer the boundary itself.

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?

The source rules implicitly guide usage ('auto' = measured when the window is in the past, otherwise forecast), which helps decide how to call it. However, there is no statement of when to prefer this tool over spot_price or best_hours, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools