Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Combine PVWatts system loss percentages

solar-design_system-loss-stack
Read-onlyIdempotent

Combine individual loss percentages into a total system loss using PVWatts multiplicative derating, with optional defaults for missing categories. Price $0.01 USDC. POST /api/v1/solar-design/system-loss-stack. 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-design_system-loss-stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
lossesNolosses, object. Required.
useDefaultsForMissingNouseDefaultsForMissing, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
derateNoderate. Number.
sourcesNosources. Array.
limitationsNolimitations. Array.
totalPercentNototalPercent. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new behavioral context: the x402 payment gate, the cost, and that an unpaid call returns payment terms without executing. It still doesn't disclose which default percentages are substituted or what the response contains.

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 short, front-loaded sentences: purpose and method first, cost and endpoint second, payment failure behavior last. 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?

Output schema exists so return values needn't be explained, and payment semantics plus annotations cover most of an agent's needs for a two-parameter aggregation tool. The only gap is not naming which categories get defaults when useDefaultsForMissing is true.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real semantic value by specifying that losses combine multiplicatively (PVWatts derating) rather than additively, which changes how the agent should interpret the losses object, plus it clarifies the purpose of useDefaultsForMissing.

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 and resource ("Combine individual loss percentages into a total system loss") and names the method (PVWatts multiplicative derating), which immediately distinguishes it from sibling loss tools like horizon-shading-loss that compute a single category.

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 the math described (aggregate per-category losses into a total) and by the "optional defaults for missing categories" note, but the description never says when to prefer this over calling individual loss tools or what the defaults actually are.

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