Skip to main content
Glama

BRAINIAC Energy Intelligence

Get all regions

energy-intelligence_regions

Retrieve metadata for all GB regions supported by the Carbon Intensity API including region IDs and names. Price $0.01 USDC. POST /api/v1/energy-intelligence/regions. 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_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present the description carries the full burden, and it does meaningful work: it discloses the price ($0.01 USDC), the POST transport, and the failure mode ("Unpaid calls return 402 and do not run"), which tells the agent the call is authenticated/paid and non-executing on failure. It stops short of describing the response shape, caching, or rate limits.

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 short sentences, front-loaded with what is returned, then commercial and transport facts. Nothing is padded, though the raw route string partly duplicates routine metadata an agent rarely needs at selection time.

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?

For a zero-parameter, no-output-schema lookup, the definition supplies purpose, returned fields, cost, and failure behavior — everything needed to decide to call it and to interpret a 402. No significant gap remains given the tool's simplicity.

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 takes zero parameters, so there is nothing to disambiguate; the baseline applies. The description correctly avoids inventing parameter discussion and instead frames the call as parameterless enumeration.

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 and resource: "Retrieve metadata for all GB regions supported by the Carbon Intensity API including region IDs and names." The scope (all regions, GB, from the Carbon Intensity API) and the returned fields are both named, so an agent can distinguish this enumeration/reference call from siblings like energy-intelligence_regional or energy-intelligence_current without opening a schema.

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?

Usage is only implied: by describing itself as the source of region IDs and names, it signals it is the lookup step to run before a per-region query, but it never says "call this first" or names energy-intelligence_regional as the follow-up. No explicit when-not guidance either.

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