Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Transpose GHI/DNI/DHI to plane-of-array irradiance

solar-design_poa-irradiance-transpose
Read-onlyIdempotent

Compute plane-of-array irradiance with isotropic, Hay-Davies or Perez sky models and NREL SPA solar geometry from caller irradiance records. Price $0.04 USDC. POST /api/v1/solar-design/poa-irradiance-transpose. 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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "tilt": "<tilt>",
      "azimuth": "<azimuth>",
      "records": "<records>"
    },
    "name": "solar-design_poa-irradiance-transpose"
  }
}

Input Schema

NameRequiredDescriptionDefault
tiltYestilt, number, from 0 to 90. Required.
modelNomodel, string, one of isotropic, haydavies, perez. Required.perez
albedoNoalbedo, number, from 0 to 1. Required.
deltaTNodeltaT, number. Required.
azimuthYesazimuth, number, from 0 to 360. Required.
recordsYesrecords, array. Required.
latitudeYeslatitude, number, from -90 to 90. Required.
elevationNoelevation, number. Required.
longitudeYeslongitude, number, from -180 to 180. Required.
pressurePaNopressurePa, number. Required.
temperatureCNotemperatureC, number. Required.

Output Schema

NameRequiredDescriptionDefault
recordsNorecords. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-annotation detail: a $0.04 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms and does not execute — a key behavioral trait for callers. It stops short of describing model-selection effects or input validation behavior.

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 compact sentences, front-loaded with the computational purpose before the commercial and endpoint details. The endpoint path sentence is somewhat mechanical but earns its place by anchoring the x402 payment note that follows.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and payment/auth behavior is covered. However, for an 11-parameter scientific computation the description omits irradiance units, the timestamp format expected in each record, and any note on how records are ordered or how sky-model choice affects results.

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 names the three model options, but that duplicates the enum, and it adds no guidance on units (W/m2 vs Wh/m2), the expected format of the `time` string, or the role of deltaT/pressurePa/temperatureC in the SPA calculation.

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 concrete verb and resource ('Compute plane-of-array irradiance') and names the three selectable sky models plus the NREL SPA geometry, so the operation is unambiguous. It does not explicitly contrast itself with siblings such as energy-yield-estimate, leaving that distinction to inference.

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?

'from caller irradiance records' implies this is the step that consumes GHI/DNI/DHI input, hinting at where it sits in a workflow, but no when-to-use or when-not-to-use conditions are stated. No alternative tools are named, so an agent must infer that transposition precedes yield estimation.

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