Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Compute inter-row spacing and GCR

solar-design_row-spacing
Read-onlyIdempotent

Compute row height, shadow gap, row pitch and ground coverage ratio that avoid row-to-row shading at a design sun position. Price $0.02 USDC. POST /api/v1/solar-design/row-spacing. 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": {
      "moduleSlopeLength": "<moduleSlopeLength>",
      "tilt": "<tilt>"
    },
    "name": "solar-design_row-spacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
sunNosun, object. Optional.
tiltYestilt, number, from 0 to 90. Required.
latitudeNolatitude, number, from -90 to 90. Optional.
elevationNoelevation, number. Required.
longitudeNolongitude, number, from -180 to 180. Optional.
designTimesNodesignTimes, array. Optional.
groundSlopeNogroundSlope, number. Required.
arrayAzimuthNoarrayAzimuth, number, from 0 to 360. Required.
moduleSlopeLengthYesmoduleSlopeLength, number. Required.

Output Schema

NameRequiredDescriptionDefault
gcrNogcr. Number.
sourcesNosources. Array.
rowPitchNorowPitch. Number.
rowHeightNorowHeight. Number.
shadowGapNoshadowGap. Number.
sunAzimuthNosunAzimuth. Number.
limitationsNolimitations. Array.
sunElevationNosunElevation. Number.

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?

The annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding behavior they cannot express: a fixed $0.02 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms without executing. That failure-mode disclosure is exactly the kind of thing an agent needs before spending a call, though nothing is said about response format or limits.

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 sentences, front-loaded with what is computed, then cost, then endpoint, then the payment caveat. No filler and no repetition of the title or schema.

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?

For a nine-parameter nested-input tool with full schema coverage and an output schema, the description supplies the outputs, pricing, transport, and payment-gate behavior, which is most of what is missing from structured fields. A hint about default sun/design-time behavior or units would have closed the remaining gap.

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 nine parameters including the nested sun object are already documented structurally. The phrase 'at a design sun position' loosely ties to the sun/designTimes inputs but adds no units, defaults, or interaction detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

The description uses a specific verb ('Compute') and enumerates the exact outputs: row height, shadow gap, row pitch, and ground coverage ratio, plus the governing condition ('avoid row-to-row shading'). That is far more informative than the title alone. It does not name a sibling to contrast with, so it stops short of a 5.

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?

It implies the use case ('at a design sun position') so an agent can infer this is the geometry/layout step, but it gives no explicit when-to-use versus when-not guidance and never points to adjacent tools such as horizon-shading-loss or module-layout-fit. Usage is implied rather than stated.

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