Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Size PV module strings for an inverter MPPT

solar-design_string-sizing
Read-onlyIdempotent

Compute minimum and maximum modules per series string and maximum parallel strings per MPPT from module temperature coefficients, site temperatures and inverter DC limits. Price $0.03 USDC. POST /api/v1/solar-design/string-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": {
      "module": "<module>",
      "site": "<site>",
      "inverter": "<inverter>"
    },
    "name": "solar-design_string-sizing"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYessite, object. Required.
moduleYesmodule, object. Required.
inverterYesinverter, object. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
feasibleNofeasible. Boolean.
iscAtTmaxNoiscAtTmax. Number.
vmpAtTmaxNovmpAtTmax. Number.
vmpAtTminNovmpAtTmin. Number.
vocAtTminNovocAtTmin. Number.
limitationsNolimitations. Array.
minModulesByMpptNominModulesByMppt. Number.
recommendedRangeNorecommendedRange. Array.
maxStringsPerMpptNomaxStringsPerMppt. Number.
maxModulesByMpptUpperNomaxModulesByMpptUpper. Number.
maxModulesBySystemVoltageNomaxModulesBySystemVoltage. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses two substantive behaviors an agent cannot get from structured fields: the $0.03 USDC charge and the fact that an unpaid call returns x402 payment terms without executing. It still says nothing about failure modes for infeasible module/inverter combinations, which matters for a sizing computation.

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?

The computation statement is front-loaded, followed by price and the payment-gating rule, so every sentence carries information an agent needs before calling. The raw endpoint path is the weakest element, useful only for transport-level debugging, but it costs little.

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 an output schema present, return values need no explanation, and the description covers the input domain, cost, and payment-gating behavior. The remaining gap is methodology (which standard or assumptions the min/max voltage math uses), which would help an agent judge whether edge-case results are trustworthy.

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 carries parameter documentation and the baseline is 3. The description adds only a conceptual grouping (temperature coefficients, site temperatures, inverter DC limits) and does not clarify the unit-enum semantics or the optional maxIscPerMppt/maxInputCurrentPerMppt fields, though the schema's own descriptions are largely boilerplate.

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?

"Compute minimum and maximum modules per series string and maximum parallel strings per MPPT" names a specific verb and three concrete outputs, then names the input families (module temperature coefficients, site temperatures, inverter DC limits). No sibling tool in the list performs string sizing, so the agent can route to it unambiguously.

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 by enumerating required inputs (module, site, inverter), which tells the agent roughly when the tool applies, but it never states prerequisites, exclusions, or which sibling to use instead for adjacent tasks like dc-ac-ratio-check or nec-690-current. Guidance is inferable rather than explicit.

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