Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Size battery backup energy and inverter power

solar-design_battery-backup-sizing
Read-onlyIdempotent

Size battery energy and inverter continuous/surge power needed to back up critical loads for a target autonomy with DoD and efficiency derates. Price $0.03 USDC. POST /api/v1/solar-design/battery-backup-sizing. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "loads": "<loads>",
      "autonomyHours": "<autonomyHours>",
      "depthOfDischarge": "<depthOfDischarge>",
      "dischargeEfficiency": "<dischargeEfficiency>"
    },
    "name": "solar-design_battery-backup-sizing"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadsYesloads, array. Required.
autonomyHoursYesautonomyHours, number. Required.
inverterMarginNoinverterMargin, number. Required.
depthOfDischargeYesdepthOfDischarge, number, from any to 1. Required.
simultaneousStartNosimultaneousStart, boolean. Required.
temperatureDerateNotemperatureDerate, number, from any to 1. Required.
dischargeEfficiencyYesdischargeEfficiency, number, from any to 1. Required.
pvRechargeKwhPerDayNopvRechargeKwhPerDay, number, from 0 to any. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
limitationsNolimitations. Array.
energyNeededKwhNoenergyNeededKwh. Number.
inverterSurgeKwNoinverterSurgeKw. Number.
nominalCapacityKwhNonominalCapacityKwh. Number.
inverterContinuousKwNoinverterContinuousKw. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, idempotentHint, openWorldHint), and the description adds genuinely new behavior: a $0.03 USDC price, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms without executing. That payment-gate disclosure is exactly the kind of trait annotations cannot express; only the return payload is left unexplained, which is acceptable given 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?

Three short sentences, front-loaded with the capability before the commercial and endpoint details. The raw path restates the tool name and is mildly redundant, but the price and unpaid-call behavior in the same breath are worth the words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter but fully documented schema with an output schema present, the description covers all that an agent needs to decide and call: what is computed, the required conceptual inputs, the cost, and the failure mode of not paying. Nothing material is missing.

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 schema already documents all 8 parameters, establishing a baseline of 3. The description adds light semantic framing by naming the derate concepts (DoD, efficiency, surge vs continuous power) that map to specific fields, but supplies no units, bounds, or defaults beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (size) and precise resources (battery energy, inverter continuous/surge power) plus the sizing basis (critical loads, target autonomy, DoD and efficiency derates). This is specific enough that an agent can distinguish it from siblings like energy-yield-estimate or string-sizing without opening the schema.

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 description implies the usage context (backing up critical loads for a target autonomy) and discloses the cost gate, but never says when to prefer this over alternatives such as energy-yield-estimate, nor any prerequisites for the inputs beyond naming the derate factors. Usage is inferable but not explicitly guided.

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