Skip to main content
Glama

VoltPlan Wiring Diagrams

Cable Cross-Section & Resistance Calculator

calculate_wire_gauge

Calculate the recommended wire gauge / cable cross-section for a DC circuit. Considers both ampacity (current carrying capacity) and voltage drop to recommend the optimal cable size. Also returns total resistance, power loss, and a fuse recommendation. Supports copper conductors from 0.75 mm² (18 AWG) to 240 mm² (300 MCM).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
powerNoLoad power in watts. Will be converted to current using the voltage. Provide either current or power.
currentNoLoad current in amps. Provide either current or power.
voltageYesSystem voltage in volts (e.g. 12, 24, 48)
isRoundTripNoAccount for both positive and negative conductor (default: true). Set to false for chassis-ground returns.
cableLengthMYesOne-way cable length in meters
temperatureCelsiusNoAmbient temperature in °C (default: 20°C). Affects copper resistance.
maxVoltageDropPercentNoMaximum acceptable voltage drop in percent (default: 3%)

Schema Changelog

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

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Discloses key behaviors: considers ampacity and voltage drop, returns resistance, power loss, fuse recommendation, and supports copper conductors from 0.75 mm² to 240 mm². No annotations to contradict, but could mention output format or algorithm assumptions.

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 concise sentences: main action, what it considers, and what it returns. No fluff, well-structured, and front-loaded.

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 the complexity of 7 parameters and no output schema, the description provides a good high-level overview. However, it does not specify output format or that it selects from standard cable sizes, leaving some gaps.

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%, so parameters are well-described in schema. The description adds contextual value by explaining why parameters like temperature and voltage drop are relevant for ampacity and voltage drop calculations.

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 it calculates wire gauge for DC circuits, considering ampacity and voltage drop, and returns resistance, power loss, and fuse recommendation. It is distinct from sibling tools like battery or 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 Guidelines3/5

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

No explicit guidance on when to use or not use this tool versus alternatives. While sibling tools are different, the description does not provide criteria for choosing this tool over others.

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.