Skip to main content
Glama

BRAINIAC Electricity Market & Grid Intelligence

Report renewable generation forecasts

electricity-market_renewable-generation-forecast

Report caller-supplied renewable historical and forecast megawatts, optionally enriched with World Bank renewable series. Future MW are never invented. Price $0.05 USDC. POST /api/v1/electricity-market/renewable-generation-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": "electricity-market_renewable-generation-forecast"
  }
}

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

B3.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description discloses important behavior: price ($0.05 USDC), payment gating ('Unpaid calls return 402 and do not run'), and data integrity ('Future MW are never invented'). It still omits return format, idempotency, and how the many input arrays are processed.

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?

Four short sentences, front-loaded with the core purpose and followed by constraint, price, endpoint, and payment behavior. No filler; each sentence adds operational information.

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 complex 16-parameter tool with nested objects, no annotations, and no output schema, the description is too thin. It covers purpose, price, and payment failure but does not explain how most inputs are used or what the report contains.

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 carry parameter meaning. It only alludes to the generation array and worldBank object, leaving bills, carbon, demand, prices, outages, tariffs, exposures, and the file/csv/text/json alternatives undocumented.

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 states a specific verb ('Report') and resource ('caller-supplied renewable historical and forecast megawatts') and adds an optional enrichment. It does not explicitly differentiate from sibling analysis tools, but the purpose is clear.

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 explicit when-to-use or when-not-to-use guidance and no named alternatives among the nine sibling tools. The optional World Bank enrichment is mentioned but without a condition for selecting it.

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