Carbon

Get Intensity

get_intensity

Read-onlyIdempotent

Check current UK electricity carbon intensity. Returns gCO2/kWh (forecast and actual) plus intensity level (very low to very high). Use to schedule energy-intensive tasks during low-carbon periods.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	End time of the intensity period (ISO 8601)
`from`	Yes	Start time of the intensity period (ISO 8601)
`index`	Yes	Intensity index level (e.g., very low, low, moderate, high, very high)
`actual_gco2_per_kwh`	Yes	Actual carbon intensity in grams CO2 per kilowatt-hour, or null if not available
`forecast_gco2_per_kwh`	Yes	Forecasted carbon intensity in grams CO2 per kilowatt-hour

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "actual_gco2_per_kwh": {
+      "description": "Actual carbon intensity in grams CO2 per kilowatt-hour, or null if not available",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "forecast_gco2_per_kwh": {
+      "description": "Forecasted carbon intensity in grams CO2 per kilowatt-hour",
+      "type": "number"
+    },
+    "from": {
+      "description": "Start time of the intensity period (ISO 8601)",
+      "type": "string"
+    },
+    "index": {
+      "description": "Intensity index level (e.g., very low, low, moderate, high, very high)",
+      "type": "string"
+    },
+    "to": {
+      "description": "End time of the intensity period (ISO 8601)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "from",
+    "to",
+    "forecast_gco2_per_kwh",
+    "actual_gco2_per_kwh",
+    "index"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {}
+]
```
First observedApr 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, but the description adds useful behavioral details like returning forecast and actual values and the intensity level range. This goes beyond annotations by explaining the output semantics without contradicting them.

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?

Two sentences, first states purpose and return values with specific units, second gives a primary use case. No wasted words, well front-loaded.

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

Completeness5/5

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

Given the tool is a simple no-parameter read, the description fully covers what it does, what it returns, and why it might be used. The output schema exists but the description already explains the key return fields (forecast, actual, level).

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 has zero parameters, and the schema is 100% covered (empty). The description adds the contextual meaning of 'current' (as opposed to historical or regional), which is inherently the parameter space. Although it doesn't explicitly state 'no parameters,' the description implies that only current data is returned, which is enough.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool checks current UK electricity carbon intensity, with specific output units (gCO2/kWh) and forecast/actual distinction. It distinguishes itself from siblings like get_intensity_by_date and get_regional_intensity by specifying 'current UK' and the return of both forecast and actual readings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use it 'to schedule energy-intensive tasks during low-carbon periods,' which is a clear use case. It doesn't mention alternatives or exclusions, but for a simple no-parameter tool, this is sufficient context for typical usage.

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

All Carbon tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.