Skip to main content
Glama

BRAINIAC Solar, Battery & Distributed Energy Intelligence

Estimate battery state of health

solar-battery_state-of-health-estimate
Read-onlyIdempotent

Estimate battery SOH from supplied sohPct or measured versus nameplate energy before you finalise a solar or battery design. Missing capacities are not invented. Call with optional text, json, csv, file, generation, panels and others. Returns checkedAt, assetCount, items, paidProviderUsed, apiKeyRequired, cloudPlatformUsed, warrantyCoverageDetermined. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you finalise a solar or battery design, text, csv, file, generation, panels, inverterEvents, batteryCycles, batteryHealth, warranties, efficiencyPeriods, consumption, assets, faultMap, asOf.

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_state-of-health-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.
assetCountNoassetCount. Number.
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 declare readOnly/idempotent/non-destructive, but the description adds real behavioral facts: missing capacities are not fabricated, results may route through a paid provider (paidProviderUsed, cloudPlatformUsed, apiKeyRequired), and HTTP 200 responses are billed even when status is partial or failed while 4xx/5xx are free. That billing detail is materially useful and is not in any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening purpose and pricing sentences are front-loaded and useful, but the trailing "Keywords:" block is raw keyword stuffing that largely duplicates the parameter list, and "and others" is vague filler. Roughly a third of the text does not earn its place.

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?

With an output schema present, the return-field enumeration is redundant but harmless, and the billing and no-fabrication notes cover the main behavioral risk. The one gap is the lack of any guidance on which of the 15 nested collections are needed to produce a meaningful estimate, which matters for a zero-required-parameter tool.

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%, so the schema already documents all 15 parameters and a 3 is the baseline. The description does add semantic context by naming sohPct and the measured-versus-nameplate comparison as the core inputs, but it never explains how the many array inputs (assets, generation, batteryCycles, warranties) relate to one 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 gives a specific verb and resource ("Estimate battery SOH") and even states the input basis: supplied sohPct, or measured versus nameplate energy. It does not distinguish itself from close siblings such as cycle-aging-analyze or round-trip-efficiency, so it falls short of a 5.

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?

It supplies a timing cue — "before you finalise a solar or battery design" — which implies when to reach for it. There is no explicit when-not guidance and no sibling tool is named as an alternative, so the agent must infer routing from names alone.

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