Skip to main content
Glama

BRAINIAC Energy Intelligence

Get current carbon intensity

energy-intelligence_current

Retrieve current GB electricity carbon intensity from the Carbon Intensity API. Supports optional regional filtering. Price $0.02 USDC. POST /api/v1/energy-intelligence/current. 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_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does well on operational traits: it discloses cost ($0.02 USDC), the endpoint, and that unpaid calls return 402 without executing. It says nothing about data freshness, update cadence, or what the response contains, which matters for a real-time intensity tool.

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?

Four short sentences, front-loaded with purpose, then cost, endpoint and payment-failure behavior. The endpoint path is arguably the least useful sentence for an agent, but nothing is bloated.

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 single-optional-parameter read tool with no output schema, the definition covers cost, invocation path and failure mode. The remaining gap is region semantics and what values come back, which the absent output schema would otherwise have carried.

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

Parameters2/5

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

One parameter with 0% schema description coverage, so the description must compensate. 'Supports optional regional filtering' only hints that the parameter exists; it never explains what regionId values mean (integers 1-18), that the default is GB-wide, or where valid IDs come from.

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?

States a specific verb and resource: 'Retrieve current GB electricity carbon intensity from the Carbon Intensity API.' The word 'current' implicitly separates it from the forecast and historical siblings, but the overlap with energy-intelligence_regional (via the regionId filter) is never addressed.

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 the word 'current' — an agent can infer this is the live-value call rather than the forecast. There is no explicit when-not guidance, especially no statement about when to use energy-intelligence_regional instead of the optional regionId filter here.

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