Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Compare module datasheet metrics

solar-design_module-spec-compare
Read-onlyIdempotent

Normalise and compare module datasheet values for efficiency, W/m², temperature-adjusted power, price per watt and warranty retention. Price $0.02 USDC. POST /api/v1/solar-design/module-spec-compare. 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": {
      "modules": "<modules>"
    },
    "name": "solar-design_module-spec-compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
modulesYesmodules, array. Required.
referenceCellTempNoreferenceCellTemp, number. Required.

Output Schema

NameRequiredDescriptionDefault
modulesNomodules. Array.
rankingNoranking. Object.
sourcesNosources. 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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-structured behavior: a $0.02 USDC cost, the POST endpoint, and critically that an unpaid call returns x402 payment terms without executing — that last point materially changes how an agent must sequence its calls. Return-shape details are left to the output schema.

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 and metrics before the commercial/transport details. Nothing is padded, though the raw endpoint path is marginally redundant for an agent that just needs to call the tool.

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?

The tool is a paid, read-only, idempotent comparison endpoint with a full output schema and 100% schema coverage, so most structure is carried elsewhere; the description supplies the payment and non-execution semantics that the structured fields cannot. Only minor gaps remain, such as error behavior on malformed module arrays or limits on comparison size.

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 coverage is 100%, so the baseline is 3, and the description does slightly better than baseline by naming the derived quantities, which tells the agent why optional fields like noct, tempCoeffPmax, price, width/height and warrantyYear25Retention matter. It does not explain referenceCellTemp (default 45) or how the nested per-module fields interact, so it does not fully replace the terse schema docs.

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 gives a specific verb ('Normalise and compare') and a specific resource ('module datasheet values'), and it enumerates the computed metrics (efficiency, W/m², temperature-adjusted power, price per watt, warranty retention), so the agent knows exactly what the tool returns. It never explicitly distinguishes itself from the many analysis siblings (layout-fit, string-sizing, payback), 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?

Usage is implied by the metric list — the agent can infer this is the tool for side-by-side module comparison — but there is no explicit 'use this when…, use X instead' routing or prerequisite statement. The only hard guidance given is the payment condition, not task selection.

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