Skip to main content
Glama

BRAINIAC Solar, Battery & Distributed Energy Intelligence

Compare distributed energy assets

solar-battery_asset-compare
Read-onlyIdempotent

Compare supplied solar/storage assets on generation deviation, SOH, efficiency, and self-consumption metrics derived only from caller records. Price $0.05 USDC. POST /api/v1/solar-battery/asset-compare. 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_asset-compare"
  }
}

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.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing price ($0.05 USDC), the POST endpoint, and crucially that an unpaid call returns x402 payment terms without executing. That payment-gate behavior is exactly the kind of thing an agent cannot infer from readOnlyHint/idempotentHint. Missing only what a successful response contains and how partial input is handled.

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

Conciseness5/5

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

Three tight sentences: what it computes, what it costs, and the failure mode. Purpose is front-loaded and every sentence carries distinct information with no filler.

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 15 optional parameters, an output schema, and full annotations, the description only needs to cover purpose, cost, and the payment gate, and it does. The gap is that with zero required parameters it never states what minimal input is needed for a meaningful comparison.

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 the baseline is 3. The description adds only the indirect hint that inputs are caller records and that the four metric families correspond to the generation/batteryHealth/efficiencyPeriods/consumption arrays; it gives no explicit field-to-metric mapping or date semantics for asOf.

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?

Names a specific verb (Compare) and resource (solar/storage assets) plus the exact metrics computed (generation deviation, SOH, efficiency, self-consumption), which separates it from the single-metric siblings like state-of-health-estimate or round-trip-efficiency. It stops short of explicitly naming those alternatives as the differentiating contrast.

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 phrase 'derived only from caller records' implies the tool needs caller-supplied data rather than lookups, which is a real usage constraint. However, there is no explicit when-to-use/when-not guidance versus the sibling analyzers, so the agent must infer that this is the multi-metric comparison entry point.

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