Skip to main content
Glama

carbon_intensity_forecast

Read-onlyIdempotent

Retrieves a 24-hour forecast of UK grid carbon intensity so you can plan energy use or automation around lower-carbon periods.

Instructions

Get 24-hour forecast of UK grid carbon intensity.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds the 24-hour horizon, which is real context, but says nothing about return format, units (e.g. gCO2/kWh), sampling interval, or freshness of the underlying data.

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 front-loaded sentence with zero filler; the scope qualifiers (24-hour, UK grid) are exactly the disambiguating information an agent needs and nothing 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?

For a no-parameter, read-only fetch with no output schema, the description conveys what one gets back at a high level (a 24-hour carbon intensity forecast for the UK grid). It stops short of the response shape and units, the one meaningful gap left when schema and annotations carry the rest.

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?

Zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly implies a no-argument call by not mentioning any inputs.

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?

States a specific verb ('Get') and resource ('24-hour forecast of UK grid carbon intensity') with both the horizon and geographic scope named. The word 'forecast' cleanly separates it from carbon_intensity_current despite no explicit sibling reference.

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 word 'forecast' implicitly signals when to use it over a current-reading tool, but the description never names carbon_intensity_current or carbon_intensity_generation as alternatives, nor states exclusions. An agent must infer the routing decision from naming alone.

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