Skip to main content
Glama

BRAINIAC Energy Intelligence

Get carbon intensity forecast

energy-intelligence_forecast

Retrieve forecast carbon intensity data from the Carbon Intensity API. Supports regional filtering. Price $0.03 USDC. POST /api/v1/energy-intelligence/forecast. 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_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
regionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 disclose important operational facts: a $0.03 USDC cost, a 402 on unpaid calls, and that unpaid calls do not execute. It omits return shape, rate limits, and the behavior when regionId or the date range is omitted, so meaningful gaps remain.

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 with purpose front-loaded and no filler. The raw endpoint string is marginal value for an agent but does not bloat the text.

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?

For a 3-parameter tool with no annotations and no output schema, the description covers the commercial/gating behavior well but leaves parameter defaults and the returned forecast structure unexplained, which an agent would need to call it confidently.

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?

Schema description coverage is 0%, and the description only alludes to one of three parameters via 'Supports regional filtering'. It says nothing about what from/to mean, their interaction, or what happens when regionId is absent (all regions vs national aggregate).

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 forecast carbon intensity data) and names the upstream source. The word 'forecast' implicitly separates it from siblings like 'current' and 'historical', though no sibling is named explicitly.

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' plus the price/payment sentences imply when this tool applies (future-looking data, paid calls only), but there is no explicit statement of when to prefer it over energy-intelligence_current or energy-intelligence_historical, and no note on defaults.

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