Skip to main content
Glama

BRAINIAC Solar, Battery & Distributed Energy Intelligence

Build solar battery performance report

solar-battery_performance-report
Read-onlyIdempotent

Aggregate generation deviation, degradation, inverter faults, cycle aging, SOH, warranty, efficiency, self-consumption, and asset comparison from caller-supplied records only. Price $0.08 USDC. POST /api/v1/solar-battery/performance-report. An unpaid call returns the x402 payment terms and does 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": "solar-battery_performance-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
assetsNoassets, array. Optional.
panelsNopanels, array. Optional.
faultMapNofaultMap, array. Optional.
generationNogeneration, array. Optional.
warrantiesNowarranties, array. Optional.
consumptionNoconsumption, array. Optional.
batteryCyclesNobatteryCycles, array. Optional.
batteryHealthNobatteryHealth, array. Optional.
inverterEventsNoinverterEvents, array. Optional.
efficiencyPeriodsNoefficiencyPeriods, array. Optional.

Output Schema

NameRequiredDescriptionDefault
asOfNoasOf. String.
statusNostatus. String.
findingsNofindings. Array.
sectionsNosections. Object.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
cloudPlatformUsedNocloudPlatformUsed. Boolean.
warrantyCoverageDeterminedNowarrantyCoverageDetermined. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds real behavioral facts the annotations do not: a fixed $0.08 USDC price, the concrete POST endpoint, and the critical fact that an unpaid call returns x402 payment terms without executing. The billing gate is exactly the kind of thing an agent needs before invoking. It stops short of 4+ territory only because nothing is said about behavior on partial or empty record sets.

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 short sentences, front-loaded with the what, then price, then endpoint, then the payment failure mode. The long domain enumeration is justified because it doubles as the report's coverage statement. Slight redundancy between the title-derived framing and the sentence itself, but no filler prose.

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?

The output schema exists, so return values need not be explained, and payment plus endpoint behavior is covered. However, for a 15-parameter, deeply nested aggregation tool with every parameter optional, the description does not say what happens when inputs are sparse, whether missing sections are skipped or reported as gaps, or how "asOf" governs the report window — gaps an agent would need resolved before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and all 15 parameters are documented in the schema itself, so the baseline is 3. The description adds only the framing that inputs are caller-supplied records; it gives no guidance on which of the many optional arrays (generation, consumption, batteryCycles, batteryHealth, inverterEvents, efficiencyPeriods, warranties, panels, assets, faultMap) are needed to produce which parts of the report, leaving the agent to guess-select among 15 optional top-level params.

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 ("Aggregate") and enumerates the exact analytical outputs — generation deviation, degradation, inverter faults, cycle aging, SOH, warranty, efficiency, self-consumption, asset comparison — which map one-to-one onto the sibling tool names, making the composite nature evident. What keeps it from a 5 is that it never states the contrast outright (that siblings do single-domain analysis, this one does all of them at once); the agent must infer the routing from the enumeration.

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?

"from caller-supplied records only" is genuinely useful scoping: it tells the agent no data fetching or external lookup occurs, so the caller must pass the records. Payment behavior is also stated. But there is no explicit statement of when to prefer this tool over the nine single-domain siblings, nor what minimum set of inputs is needed to get a meaningful report.

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