Skip to main content
Glama

BRAINIAC Energy Intelligence

Get energy intelligence report

energy-intelligence_report

Generate a comprehensive energy intelligence report combining current intensity, regional data, and generation mix from the Carbon Intensity API. Price $0.05 USDC. POST /api/v1/energy-intelligence/report. 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_report"
  }
}

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?

No annotations are supplied, so the description carries the full burden. It does valuable work by disclosing price ($0.05 USDC), the POST transport, and the failure mode (unpaid calls return 402 and do not run), but it says nothing about latency, rate limits, idempotency, caching, or whether cost is incurred per call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, followed by cost/transport and the failure condition. Nothing is padded and the ordering lets an agent decide viability before parsing details.

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?

Reasonable for a zero-annotation, single-optional-parameter tool with no output schema; the description says what the report aggregates. However, the optional regionId's default behavior and the report's rough shape or size are left unaddressed, which matters for an agent deciding whether to pay.

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 coverage is 0% and the single regionId parameter (integer, 1–18, optional) is never explained. The description says the report includes "regional data" but does not state what regionId selects, what happens when it is omitted, or what the valid range means, so it adds no meaning beyond the bare schema.

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 ("Generate a comprehensive energy intelligence report") and names the three data sources it fuses: current intensity, regional data and generation mix. That composition implicitly separates it from the single-purpose siblings, but it never explicitly says "use this instead of calling the individual tools."

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: the agent can infer this is the aggregate/summary call, and the payment sentence establishes a prerequisite (paid call required). There is no explicit when-to-use versus energy-intelligence_current, _regional or _generation-mix, and no statement about when to prefer the cheaper single-purpose calls.

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