Skip to main content
Glama

BRAINIAC Solar, Battery & Distributed Energy Intelligence

Classify solar inverter faults

solar-battery_inverter-fault-classify
Read-onlyIdempotent

Classify supplied inverter log events using a caller fault map or keyword signals in supplied messages. Cloud catalogs are not queried. Price $0.04 USDC. POST /api/v1/solar-battery/inverter-fault-classify. 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_inverter-fault-classify"
  }
}

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.
categoriesNocategories. Array.
eventCountNoeventCount. 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?

Beyond the annotations, it discloses cost ($0.04 USDC), the payment gate ('an unpaid call returns the x402 payment terms and does not run'), and that cloud catalogs are not queried — a material behavioral constraint on the otherwise openWorld-flagged tool. This is genuinely useful context annotations cannot convey; the only gap is that the 'no cloud catalog' statement slightly narrows the openWorldHint without fully explaining the remaining external interaction (payment).

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 action and mechanism, then the constraint, price, and payment behavior. The raw route string ('POST /api/v1/...') is the only low-value element, but it is brief.

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?

An output schema exists, so return values need no explanation, and the payment behavior is covered. However, for a 15-parameter tool, the description does not hint at which of the many arrays (assets, panels, generation, batteryHealth, etc.) matter for fault classification or how the faultMap interacts with event messages, leaving an agent to infer the operative subset from the schema alone.

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 baseline is 3. The description does add a little meaning by identifying faultMap and message-bearing events as the operative inputs among 15 parameters, but it says nothing about the other data arrays or which inputs are actually used for classification.

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 and resource ('Classify supplied inverter log events') and clarifies the mechanism ('caller fault map or keyword signals in supplied messages'). It is distinguishable from the sibling analysis tools, which estimate, compare, or report rather than classify faults, though the description never names a sibling explicitly.

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?

The two classification modes (caller-supplied faultMap vs keyword matching on messages) imply how to prepare input, but there is no explicit when-to-use guidance, no statement of when this tool is the wrong choice, and no mention of prerequisites such as needing inverterEvents or a faultMap present.

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