Skip to main content
Glama
YUZU-Hub

wiring-diagram-mcp

by YUZU-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Inverter Sizing Calculator

calculate_inverter_size

Calculate the recommended inverter size for running AC loads from a DC battery system, factoring in continuous power, startup surge, and a 25% headroom.

Instructions

Calculate the recommended inverter size for running AC loads from a DC battery system. Accounts for continuous power, startup surge power (motors typically surge 2-3x), and includes a 25% headroom for the continuous rating. Returns the recommended inverter wattage and the DC current draw at system voltage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
systemVoltageYesDC system voltage (e.g. 12, 24, 48)
loadsYesList of AC loads that will run through the inverter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided; the description adequately discloses key behaviors (surge handling, 25% headroom, computed outputs) for a non-destructive calculator.

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?

Two compact sentences with no wasted words; front-loaded with core purpose.

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?

Covers inputs, calculation assumptions, and outputs; missing edge case handling but sufficient for a simple calculator tool.

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 description adds limited value beyond schema; it explains how parameters are used in calculation but no new semantic detail per parameter.

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 recommended inverter size for AC loads from a DC system, accounting for continuous power, surge, and headroom, and distinguishes it from sibling tools like calculate_battery_bank.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for inverter sizing but lacks explicit when-to-use or when-not-to-use guidance relative to siblings.

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

Deploy Server

Other Tools