Skip to main content
Glama

BRAINIAC Energy Intelligence

Get historical carbon intensity

energy-intelligence_historical

Retrieve historical or forecast carbon intensity data for a specific time period from the Carbon Intensity API. Supports regional filtering. Price $0.05 USDC. POST /api/v1/energy-intelligence/historical. 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_historical"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
regionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 it does disclose genuinely useful behavior: a $0.05 USDC price, the POST endpoint, and that unpaid calls return 402 and do not execute. It omits what happens when from/to are omitted (all three params are optional), any defaults, rate limits, and the shape of returned data.

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 the purpose before the operational details (price, endpoint, payment failure mode). No filler, though the endpoint path largely restates the tool name.

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?

Covers cost and payment gating well, which is the highest-risk unknown for an agent, but leaves the return payload, default time window, and regionId semantics unexplained for a tool with no output schema and no annotations.

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%, so the description must compensate for three undocumented parameters. It only gestures at them via "specific time period" (from/to) and "regional filtering" (regionId), adding no format, timezone, ordering, or valid-range information such as regionId's 1-18 bounds.

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 historical or forecast carbon intensity data") plus the source API and the regional filtering capability. It is distinguishable from energy-intelligence_current and energy-intelligence_regions, though the phrase "historical or forecast" blurs the line with the energy-intelligence_forecast sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over energy-intelligence_forecast or energy-intelligence_current, and the description's own "historical or forecast" wording actively muddies the choice. The only usage-adjacent information is that a time period is required in spirit, with no exclusions or prerequisites stated.

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