Skip to main content
Glama

BRAINIAC Energy Intelligence

Get regional carbon intensity

energy-intelligence_regional

Retrieve carbon intensity data for all GB regions or a specific region from the Carbon Intensity API. Includes generation mix information. Price $0.05 USDC. POST /api/v1/energy-intelligence/regional. Unpaid calls return 402 and do not run.

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": "energy-intelligence_regional"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description provides valuable operational behavior: a $0.05 USDC price, the POST endpoint, and the fact that unpaid calls return 402 without running. Retrieval implies a nonmutating operation, but safety is not stated explicitly and data freshness or response behavior remains undisclosed.

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?

The purpose is front-loaded, and each short sentence adds distinct information about scope, included data, cost, transport, or payment failure. The definition is compact without filler.

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

Completeness3/5

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

The definition is sufficient for a basic paid invocation of a simple one-parameter tool. Given the absence of annotations and an output schema, however, the missing time scope, response shape, explicit omitted-parameter behavior, and region-ID discovery guidance leave meaningful gaps.

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?

The schema has no parameter descriptions, so the all-regions-versus-specific-region wording usefully implies that regionId selects one region and can be omitted for all regions. However, that mapping is never stated explicitly, and the description does not explain what the IDs represent or how to discover them.

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 clearly states the verb and resource: retrieving carbon intensity for all GB regions or one specific region, with generation mix included. It does not explicitly distinguish its time scope or content from the current, forecast, historical, or generation-mix sibling tools.

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 GB regional scope and all-versus-specific options imply when the tool is useful. There is no explicit guidance on when to prefer it over a sibling, how its time coverage differs, or where to find valid region IDs.

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.

Resources