Skip to main content
Glama

VoltPlan Wiring Diagrams

by io.github.YUZU-Hub

Battery Bank Sizing Calculator

calculate_battery_bank

Calculate the recommended battery bank size based on daily energy consumption. Accounts for days of autonomy (how many days without charging) and depth of discharge. Returns required capacity, number of batteries, and wiring configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
systemVoltageYesTarget system voltage in volts (e.g. 12, 24, 48)
daysOfAutonomyNoDays the system should run without any charging (default: 2)
singleBatteryAhYesCapacity of a single battery in amp-hours (e.g. 100, 200)
dailyConsumptionWhYesDaily energy consumption in watt-hours (from calculate_power_budget)
singleBatteryVoltageYesVoltage of a single battery (e.g. 12.8 for LiFePO4, 12 for lead-acid)
depthOfDischargePercentNoUsable percentage of battery capacity. LiFePO4: 80-90%, AGM: 50%, Gel: 50% (default: 80)

Schema Changelog

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

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, description carries full burden. It correctly indicates the tool is a calculator returning results, but does not mention if it has side effects, authentication needs, or any assumptions about input ranges. The output format is briefly described but lacks detail on data types or structure.

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 sentences, no wasted words. First sentence states purpose and output, second adds key factors, third lists return items. Front-loaded with main action, every sentence earns its place.

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?

Given 6 parameters and no output schema, description explains inputs and outputs adequately. It references a dependency on another tool (calculate_power_budget) and covers key assumptions. However, it could be more complete by specifying units for output or constraints on wiring configuration format.

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 baseline is 3. Description adds context by summarizing how parameters (daysOfAutonomy, depthOfDischargePercent) are used together, but does not add new meaning beyond what schema already provides for each parameter individually.

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?

Description states specific verb 'calculate' with resource 'battery bank size' and mentions inputs and outputs. It clearly distinguishes from sibling tools like calculate_power_budget or calculate_solar_size by focusing on battery bank sizing alone.

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?

Description implies usage after calculate_power_budget by referencing 'daily energy consumption (from calculate_power_budget)', but does not explicitly state when to use this vs other battery-related tools like calculate_battery_config. No exclusion or alternative guidance.

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