Skip to main content
Glama

VoltPlan Wiring Diagrams

Power Budget / Energy Audit

calculate_power_budget

Calculate total daily energy consumption from a list of electrical loads. Each load specifies its power draw, how many hours per day it runs, and quantity. Returns total daily energy (Wh and Ah), peak power draw, and average power. This is typically the first step in sizing a battery bank and solar system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loadsYesList of electrical loads to include in the budget
systemVoltageYesSystem voltage in volts (e.g. 12, 24, 48)

Schema Changelog

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

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so description carries full burden. It describes the calculation and outputs (Wh/Ah, peak power, average power). For a pure calculation tool, this is adequate, though it could mention that it has no side effects (read-only).

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 sentences: first states the purpose, second gives contextual guidance. No wasted words, front-loaded with key information.

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?

No output schema, but description mentions return values (Wh, Ah, peak power, average power). Missing details on output format, but sufficient for a straightforward calculation tool. Could be improved with example or more precise return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds value by summarizing parameter usage (power draw, hours, quantity) and outputs, going beyond the schema's individual field descriptions.

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 clearly states the tool calculates total daily energy consumption from electrical loads, specifying inputs and outputs. It distinguishes itself from sibling tools by positioning it as the first step in battery/solar sizing.

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?

Description provides clear context that this is typically the first step in sizing a battery bank and solar system, guiding when to use it. However, it does not explicitly state when not to use it or mention alternatives among siblings.

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.

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.