Skip to main content
Glama

BRAINIAC Solar, Battery & Distributed Energy Intelligence

Estimate solar panel degradation

solar-battery_panel-degradation-estimate
Read-onlyIdempotent

Estimate panel degradation from supplied nameplate/prior and measured capacity over time. Missing baselines are not invented. Price $0.04 USDC. POST /api/v1/solar-battery/panel-degradation-estimate. 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_panel-degradation-estimate"
  }
}

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
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
panelCountNopanelCount. Number.
limitationsNolimitations. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
cloudPlatformUsedNocloudPlatformUsed. Boolean.
warrantyCoverageDeterminedNowarrantyCoverageDetermined. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral facts: a $0.04 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms and does not execute. It also states a policy that missing baselines are not invented, which tells the agent results are conservative rather than fabricated. Return shape is left to the output schema, which is acceptable.

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?

Five short sentences, front-loaded with the analysis purpose before the commercial and endpoint details. The telegraphic 'Missing baselines are not invented' and bare path string are efficient rather than padded. Nothing is wasted, though the payment sentences could be compressed into one.

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

Completeness4/5

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

For a complex tool with nested objects, 15 optional parameters, rich annotations and an output schema, the definition covers the essentials: what is computed, what input it draws on, cost, and payment-gate behavior. The main gap is that with zero required parameters the description never clarifies which of the many arrays (panels, assets, generation, etc.) are actually needed to produce a result.

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% across all 15 parameters, so the schema already carries the documentation burden and a baseline of 3 applies. The description's reference to nameplate/prior/measured capacity loosely maps to the panels fields but adds no syntax, format, or precedence guidance. It neither helps nor conflicts with the 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?

The description names a specific verb and resource: 'Estimate panel degradation from supplied nameplate/prior and measured capacity over time.' That is far more than a restatement of the title, and it hints at degradation-vs-capacity analysis. It does not, however, distinguish this from siblings like cycle-aging-analyze or state-of-health-estimate, so an agent cannot route between them on this text alone.

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 mention of 'supplied nameplate/prior and measured capacity over time' tells an agent roughly what input is expected. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling estimation tools. An agent must infer the selection criteria.

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