Skip to main content
Glama

Get Regional Intensity

get_regional_intensity
Read-onlyIdempotent

Carbon intensity (forecast gCO2/kWh + index band) and generation mix for a specific Great Britain region. Pass "postcode" (UK outcode, first half of a postcode, e.g. "RG10") or "regionid" (1-17, e.g. 13 = London). Omit both for all regions at the current half-hour. Regional figures are forecast-only.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postcode": "RG10"
    },
    "name": "get_regional_intensity"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeNoUK outcode (first part of a postcode), e.g. "RG10". No spaces.
regionidNoGB region id 1-17 (e.g. 13 = London).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / regionid / description
      Previous value: -"GB region id 1–17 (e.g. 13 = London)."New value: +"GB region id 1-17 (e.g. 13 = London)."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "postcode": "RG10"
      +  },
      +  {
      +    "regionid": 13
      +  }
      +]
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety behavior is covered before the description starts. The description still adds real value by disclosing that figures are forecast-only and that omitting both parameters returns all regions for the current half-hour. It says nothing about accuracy, pagination or failure modes, so it adds context but does not go far beyond the annotations.

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?

Three tight sentences with the resource and its return fields front-loaded, then the parameter options, then the default. The example values for postcode and regionid duplicate the schema descriptions, which is the only wasted space.

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?

There is no output schema, but the description compensates by naming the return contents: forecast gCO2/kWh, an index band, and generation mix. Combined with the documented default scope and forecast-only caveat, an agent can call this correctly; only error behavior for an invalid outcode or out-of-range regionid is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents postcode as a space-free UK outcode and regionid as 1-17 with 13 = London, and the description largely restates those examples. The one genuine addition is the default behavior when both parameters are omitted, which the schema does not state.

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 verb and resource: forecast carbon intensity (gCO2/kWh plus index band) and generation mix, scoped to a Great Britain region. That lets an agent separate it from the national-level get_intensity and from the pure get_generation_mix sibling, though it never names those alternatives directly.

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 description explains how to scope a call: pass postcode or regionid, and omit both to get every region for the current half-hour. It does not explain when to choose this tool over get_intensity or get_generation_mix, so selection guidance is only implied.

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.