Skip to main content
Glama

BRAINIAC Electricity Market & Grid Intelligence

Analyze electricity demand profiles

electricity-market_demand-profile-analyze

Analyze supplied demand observations for average, peak, minimum, and load factor by region. Missing megawatts are not invented. Price $0.04 USDC. POST /api/v1/electricity-market/demand-profile-analyze. 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_demand-profile-analyze"
  }
}

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 behavioral burden and adds useful details: missing megawatts are not invented, calls cost $0.04 USDC, the endpoint is POST, and unpaid calls return 402 without running. However, it does not disclose whether data is stored, what the response contains, or other side effects expected from a 16-parameter analysis tool.

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?

The description is short, front-loads the purpose, and avoids filler. The operational details about price, endpoint, and unpaid calls are relevant, though the sentences are somewhat telegraphic rather than structured.

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 tool with 16 parameters, nested objects, no annotations, and no output schema, the description is insufficient. It covers purpose, no-imputation behavior, cost, and payment failure, but does not explain how the many input sources are combined, defaults, or what an agent should expect in return.

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, including many nested arrays and objects. The description mentions demand observations and region, but leaves the roles of csv, json, text, file, feed, asOf, bills, carbon, prices, outages, tariffs, exposures, worldBank, generation, and carbonIntensity unexplained.

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 and resource: analyze supplied demand observations for average, peak, minimum, and load factor by region. It is clear what the tool computes, but it does not explicitly distinguish itself from related sibling tools such as peak-demand-charge-calculate.

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?

The description gives no explicit when-to-use or when-not-to-use guidance. It implies the tool is for demand observations but does not name alternatives or explain when another sibling tool would be more appropriate.

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