Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Estimate far-field horizon shading losses

solar-design_horizon-shading-loss
Read-onlyIdempotent

Estimate beam and isotropic sky-diffuse losses caused by a caller far-field horizon profile against sun positions and beam POA. Price $0.03 USDC. POST /api/v1/solar-design/horizon-shading-loss. 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": {
      "horizon": "<horizon>"
    },
    "name": "solar-design_horizon-shading-loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesNotimes, array. Optional.
beamPoaNobeamPoa, array. Optional.
horizonYeshorizon, array. Required.
recordsNorecords, array. Optional.
latitudeNolatitude, number, from -90 to 90. Optional.
elevationNoelevation, number. Required.
longitudeNolongitude, number, from -180 to 180. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
limitationsNolimitations. Array.
blockedHoursNoblockedHours. Number.
beamLossFractionNobeamLossFraction. Number.
skyDiffuseLossFractionNoskyDiffuseLossFraction. Number.

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 cover read-only, idempotent, open-world, non-destructive semantics, and the description adds genuinely new behavioral context: the $0.03 USDC price, the x402 payment protocol, and the fact that an unpaid call returns payment terms instead of running. Return-value behavior is not described, though 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 sentences, front-loaded with the purpose, followed by cost and endpoint facts and the failed-payment behavior. Little waste, though the raw path and price could be tighter.

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 rich annotations, 100% schema coverage, and an output schema, the description only needs to add cost, transport, and payment gating, which it does. Minor gap: it does not clarify when to use the optional 'records' vs 'times'/'latitude'/'longitude' input paths.

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 parameters are already fully documented; the description only loosely names the horizon profile, sun positions, and beam POA without adding format, ordering, or interaction details. Baseline 3 is appropriate when the schema carries the semantics.

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?

States a specific verb ('Estimate') and a precisely scoped resource ('beam and isotropic sky-diffuse losses caused by a caller far-field horizon profile against sun positions and beam POA'). An agent can tell this apart from generic yield or POA-transpose tools, though no sibling is named explicitly.

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 rather than stated: the caller must supply a horizon profile plus sun positions and beam POA, which signals the prerequisite inputs. However, there is no explicit when-to-use/when-not-to-use guidance and no routing toward alternatives such as poa-irradiance-transpose or system-loss-stack.

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