Skip to main content
Glama

BRAINIAC Solar, Battery & Distributed Energy Intelligence

Calculate battery round-trip efficiency

solar-battery_round-trip-efficiency
Read-onlyIdempotent

Calculate round-trip efficiency from supplied charge and discharge energy for each period. Price $0.03 USDC. POST /api/v1/solar-battery/round-trip-efficiency. 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_round-trip-efficiency"
  }
}

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.
periodCountNoperiodCount. 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 cover safety (readOnly, non-destructive, idempotent, open-world), and the description adds genuinely non-obvious behavior: a $0.03 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. That payment-gating behavior is the key operational fact an agent needs and is not recoverable from annotations or schema.

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?

Three short sentences with no filler: purpose first, then price, then endpoint and payment behavior. Front-loading is correct and every sentence carries information, though the endpoint path is somewhat redundant with the tool identity.

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 model is well covered. However, for a tool with 15 optional top-level parameters and nested arrays, the description does not indicate the minimum viable input shape (e.g., that efficiencyPeriods with chargeKwh/dischargeKwh is the core payload), leaving a meaningful gap for a complex schema.

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 schema already documents all 15 parameters, establishing a baseline of 3. The description adds only a light pointer to the charge/discharge-per-period inputs, without clarifying which of the many optional arrays (efficiencyPeriods vs. consumption vs. batteryCycles) actually drives the calculation.

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 ('Calculate round-trip efficiency') and names the inputs it consumes ('supplied charge and discharge energy for each period'). An agent can distinguish it from siblings like storage-self-consumption or cycle-aging-analyze, though the description never names an alternative 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?

Usage is implied by 'from supplied charge and discharge energy for each period', which tells the caller data must be provided, but there is no explicit when-to-use versus when-not statement and no routing to sibling analysis tools. The payment caveat describes mechanics, not tool selection.

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