Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Fit modules onto a roof polygon

solar-design_module-layout-fit
Read-onlyIdempotent

Maximise the number of modules on a roof-face polygon with caller setbacks, orientation, gaps and obstruction polygons. Price $0.04 USDC. POST /api/v1/solar-design/module-layout-fit. 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": {
      "roof": "<roof>",
      "setback": "<setback>",
      "module": "<module>"
    },
    "name": "solar-design_module-layout-fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapNogap, number, from 0 to any. Required.
roofYesroof, array. Required.
moduleYesmodule, object. Required.
setbackYessetback, number, from 0 to any. Required.
gridOffsetsNogridOffsets, integer, from 1 to 25. Required.
obstructionsNoobstructions, array. Required.
orientationsNoorientations, array. Required.

Output Schema

NameRequiredDescriptionDefault
bestNobest. Object.
sourcesNosources. Array.
candidatesNocandidates. Array.
placementsNoplacements. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world behavior. The description goes beyond them with two valuable facts an agent cannot infer: the $0.04 USDC price and the fact that an unpaid call short-circuits to x402 payment terms without executing. It stops short of describing result shape or failure modes, which the output schema partially covers.

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 purpose, then cost, then transport details. The raw endpoint path (POST /api/v1/...) is the weakest element—procedural plumbing rather than decision-relevant information—but it does not bloat the text materially.

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 7-parameter tool with nested objects and a published output schema, the description covers the essential things: what is computed, what inputs shape it, what it costs, and what happens without payment. Only edge-case behavior (degenerate polygons, no-fit results) is unaddressed.

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 baseline is 3. The description adds conceptual meaning by naming setbacks, orientation, gaps and obstruction polygons as the levers of the fit, but leaves gridOffsets, module width/height, and the roof polygon's coordinate format entirely to the schema.

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?

"Maximise the number of modules on a roof-face polygon" names a specific verb (maximise/fit) and resource (modules on a roof-face polygon), and the following clause lists the constraining inputs (setbacks, orientation, gaps, obstructions). This is clearly distinguishable from siblings like row-spacing or energy-yield-estimate, though it never explicitly names an alternative.

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 optimization framing, and the payment note ("An unpaid call returns the x402 payment terms and does not run") gives a concrete prerequisite for a successful call. However, there is no explicit guidance on when to choose this tool over row-spacing, string-sizing, or other layout-related siblings, nor any stated limitations on input geometry.

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