Skip to main content
Glama

BRAINIAC Electricity Market & Grid Intelligence

Build electricity market exposure report

electricity-market_exposure-report

Aggregate price, demand, carbon, tariff, volatility, renewable, outage, and exposure findings from supplied records and optional key-free public datasets. Price $0.08 USDC. POST /api/v1/electricity-market/exposure-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": "electricity-market_exposure-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
feedNo
fileNo
jsonNo
textNo
billsNo
carbonNo
demandNo
pricesNo
outagesNo
tariffsNo
exposuresNo
worldBankNo
generationNo
carbonIntensityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 valuable behavior: the $0.08 USDC price, the POST endpoint, and that unpaid calls return 402 without running. However, it says nothing about the returned report's structure, how supplied records and public datasets are merged or prioritized, or what happens on partial/invalid input.

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?

Three sentences, front-loaded with purpose, then cost, then endpoint/payment behavior. Every sentence carries information, though the endpoint string is of marginal use to an agent that already has the tool binding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter aggregation tool with nested objects, zero schema descriptions, no annotations, and no output schema, the description is far too thin. It covers payment gating but leaves input-mode selection, record semantics, and report contents entirely unspecified.

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% across 16 parameters, so the description must compensate and largely does not. It hints at 'supplied records' and 'optional key-free public datasets' (loosely mapping to csv/json/text/file and feed/worldBank/carbonIntensity), but gives no meaning for asOf, the array record types, or when to choose one input mode over another.

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 uses a specific verb, 'Aggregate', and enumerates the resources combined (price, demand, carbon, tariff, volatility, renewable, outage, exposure), making the tool's role as a composite report builder clear. It implicitly distinguishes itself from the single-domain sibling tools by covering all domains at once, though it never names or contrasts them explicitly.

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?

There is no statement of when to use this tool versus the nine sibling analysis tools, no prerequisites, and no exclusions. The only conditional information is payment-related (unpaid calls return 402), which is a gate, not usage guidance.

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