Skip to main content
Glama

BRAINIAC Energy Intelligence

Get generation mix

energy-intelligence_generation-mix

Retrieve electricity generation mix data showing fuel type proportions from the Carbon Intensity API. Supports regional and time-based filtering. Price $0.03 USDC. POST /api/v1/energy-intelligence/generation-mix. 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_generation-mix"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
regionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/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 meaningful work: it discloses the paid nature ($0.03 USDC), the underlying endpoint (POST /api/v1/energy-intelligence/generation-mix), and crucially that unpaid calls return 402 and do not execute. It stops short of return shape, pagination, or coverage boundaries, but the payment-failure behavior is exactly the kind of operational detail an agent needs.

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, followed by pricing, endpoint, and the payment-failure rule. Every sentence carries distinct information; nothing is padded.

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, unannotated, output-schema-less tool, the definition covers purpose and the paid-call mechanics well. It leaves gaps on parameter formats, default/empty-filter behavior, and what the response contains, which matter because 0% of parameters are documented elsewhere.

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 and only partially does. 'Regional and time-based filtering' loosely maps to regionId and from/to, but nothing explains that timestamps must be ISO-8601 with a Z suffix, that regionId is bounded 1-18, or what happens when all three optional parameters are omitted.

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 names a specific verb and resource: 'Retrieve electricity generation mix data showing fuel type proportions'. That is clearly distinct from siblings such as current, forecast, historical, and regions. It does not explicitly contrast itself with the closest alternatives like energy-intelligence_historical or energy-intelligence_regional, but the resource itself is identifiable.

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?

'Supports regional and time-based filtering' hints at usage but gives no when-to-use guidance, no exclusion conditions, and no routing advice relative to the six sibling tools. An agent must infer whether this or energy-intelligence_historical/regional is the right call.

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