Skip to main content
Glama

BRAINIAC Solar PV Design Calculations

Parse PVsyst PAN or OND text files

solar-design_pan-ond-parse
Read-onlyIdempotent

Parse PVsyst PAN (module) and OND (inverter) text files into nested raw JSON and a normalised datasheet object. Price $0.02 USDC. POST /api/v1/solar-design/pan-ond-parse. 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": {
      "fileType": "<fileType>",
      "content": "<content>"
    },
    "name": "solar-design_pan-ond-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYescontent, string, length 1 to 524288. Required.
fileTypeYesfileType, string, one of pan, ond. Required.

Output Schema

NameRequiredDescriptionDefault
rawNoraw. Object.
sourcesNosources. Array.
normalizedNonormalized. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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-obvious behavior: a $0.02 USDC price, the concrete POST endpoint, and the important fact that an unpaid call returns x402 payment terms without executing the parse. It does not describe input validation failures or the size/format limits beyond the schema's maxLength.

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 the purpose, then cost and endpoint, then the payment-failure behavior. No filler; every sentence carries a distinct fact an agent needs (what it does, what it costs, what happens if unpaid).

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 an output schema present, the description need not enumerate return fields, and annotations cover safety. It closes the gaps that structured fields cannot express: pricing, the transport path, and the unpaid-call no-op. Only the file-content format convention is left unstated.

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%, with both parameters documented and the fileType enum spelled out as pan/ond, so the baseline is 3. The description does not clarify whether 'content' is raw file text versus a path or base64 blob, nor what distinguishes a PAN from an OND file semantically.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Parse) and specific resources (PVsyst PAN module files and OND inverter files), plus the two output forms (nested raw JSON and a normalised datasheet object). This clearly separates it from the sibling sizing/yield/financial calculators, none of which ingest PVsyst files.

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 only implied by the input contract: you supply file content of type pan or ond. There is no explicit statement of when an agent should reach for this versus other tools, no prerequisite about which file type to use for which data, and no exclusions. The only stated condition is the payment gate.

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