Skip to main content
Glama

BRAINIAC Solar, Battery & Distributed Energy Intelligence

Check battery warranty thresholds

solar-battery_warranty-threshold-check
Read-onlyIdempotent

Compare supplied SOH, cycles, and calendar age to caller-supplied warranty thresholds. Legal warranty coverage is not determined. Price $0.03 USDC. POST /api/v1/solar-battery/warranty-threshold-check. 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_warranty-threshold-check"
  }
}

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.
limitationsNolimitations. Array.
warrantyCountNowarrantyCount. Number.
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/openWorld, so the safety profile is covered elsewhere. The description adds material behavior beyond that: the $0.03 USDC price, the x402 payment gating, and specifically that an unpaid call returns payment terms and does not execute. That last point is important and non-obvious. It does not describe output shape, but an output schema exists.

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 purpose before the disclaimer, pricing, and payment behavior. The endpoint path 'POST /api/v1/solar-battery/warranty-threshold-check' is the only line that arguably does little work for an MCP caller. Overall there is no padding and no repetition.

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?

Safety is covered by annotations and return values by the output schema, so the main remaining burden is payment handling, which the description handles well. For a 15-parameter tool with nested arrays (batteryHealth, batteryCycles, warranties, plus four interchangeable input channels), the description gives no guidance on assembling the input, leaving a meaningful gap for such a complex signature.

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%, but the schema text is largely mechanical ('sohPct, number, from 0 to 100. Optional.'), so the description carries real semantic mapping by naming SOH, cycles, and calendar age against caller-supplied warranty thresholds. It does not clarify the four alternative payload modes (csv/json/text/file) or how asOf interacts with the comparison, so it does not fully compensate for the schema's thin prose.

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 pair: 'Compare supplied SOH, cycles, and calendar age to caller-supplied warranty thresholds.' The scope disclaimer 'Legal warranty coverage is not determined' further narrows what the tool is and is not, which separates it from interpretive siblings like state-of-health-estimate. It stops short of naming any sibling explicitly, so an agent must still infer the boundary.

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?

There is one genuine exclusion cue, 'Legal warranty coverage is not determined,' which tells an agent not to use this for legal warranty decisions. However, no alternative tool is named and no guidance is given on when this comparison is preferred over the sibling analyses. Usage is implied by the purpose rather than stated.

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