Skip to main content
Glama

BRAINIAC Solar, Battery & Distributed Energy Intelligence

Analyze battery cycle aging

solar-battery_cycle-aging-analyze
Read-onlyIdempotent

Analyze supplied battery cycle counts, depth of discharge, and throughput. Rated cycle life is used only when supplied. Price $0.04 USDC. POST /api/v1/solar-battery/cycle-aging-analyze. 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_cycle-aging-analyze"
  }
}

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot express: a $0.04 USDC charge, and that an unpaid call returns x402 payment terms without executing, plus the fallback rule that rated cycle life is only used when supplied.

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?

Four short sentences, front-loaded with the analytical purpose; payment and endpoint details follow. Nothing is padded, though the raw POST path is low-value boilerplate for an MCP caller.

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?

For a tool with 15 optional parameters, deep nested arrays, and a rich output schema, the description covers purpose and billing but leaves a real gap: it never says which of csv/json/text/file payload forms to use, nor that all parameters are optional and at least one data source is presumably required.

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 coverage is 100%, so every one of the 15 parameters is already documented, albeit with thin mechanical descriptions (name, type, length). The description maps its subject matter onto batteryCycles fields (cycleCount, depthOfDischargePct, throughputKwh) and ratedCycles, adding modest meaning, but says nothing about the csv/json/text/file input alternatives an agent must choose between.

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?

States a specific verb (Analyze) and resource (battery cycle aging) and enumerates the driving inputs: cycle counts, depth of discharge, throughput. That distinguishes it reasonably well from siblings like state-of-health-estimate, though it never names a sibling or explicitly contrasts the two aging models.

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 by the data it consumes — an agent infers it should call this when it has cycle/DoD/throughput records. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as state-of-health-estimate for SoH-based analysis.

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