Skip to main content
Glama

VoltPlan Wiring Diagrams

by io.github.YUZU-Hub

Solar Panel Sizing Calculator

calculate_solar_size

Calculate the required solar panel wattage to cover daily energy consumption. Accounts for peak sun hours at the location and system efficiency losses (MPPT conversion, wiring, temperature derating). Returns required wattage and common panel configurations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
peakSunHoursYesAverage daily peak sun hours for the location. Examples: Northern Europe winter 1-2h, summer 4-6h. Southern US 5-6h. Equatorial regions 5-7h.
systemEfficiencyNoOverall system efficiency factor (default: 0.85). Accounts for MPPT losses, wiring losses, temperature derating, and panel soiling.
dailyConsumptionWhYesDaily energy consumption in watt-hours (from calculate_power_budget)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains what the tool accounts for (efficiency losses) but does not mention whether it has side effects, is read-only, or any authentication or rate-limit considerations.

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?

The description is two sentences long with no unnecessary words. It front-loads the purpose and concisely lists inputs and outputs.

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 3-parameter calculator without output schema, the description covers inputs and general output. However, it vaguely mentions 'common panel configurations' without detailing the output structure, leaving some ambiguity.

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%, and the schema already describes each parameter with examples and defaults. The description adds context about efficiency losses but does not significantly enhance parameter understanding beyond the schema.

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?

The description clearly states the tool calculates required solar panel wattage based on daily consumption and peak sun hours. It distinguishes from sibling tools like calculate_power_budget by focusing on sizing panels rather than estimating consumption or battery sizing.

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?

The description implies usage when daily consumption is known (from calculate_power_budget) and when peak sun hours are available. However, it does not explicitly state when not to use or mention alternatives among sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All VoltPlan Wiring Diagrams toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct calculation or action: battery bank sizing, battery configuration, charging time, inverter sizing, power budget, solar sizing, wire gauge, wiring diagram generation, and listing component types. There is no overlap in purpose.

Naming Consistency4/5

The majority of tools use the verb 'calculate_' (7 of 9), while two tools use 'generate_' and 'list_'. This breaks the strict pattern but is still predictable and clear.

Tool Count5/5

With 9 tools, the server covers the essential calculations and diagram generation for off-grid electrical systems without feeling bloated or sparse.

Completeness4/5

The tools cover the full workflow from power budget to wiring diagram, including battery, solar, inverter, wire sizing, and charging time. Minor omissions like charge controller sizing or alternator sizing exist, but the core surface is complete.

Resources