Skip to main content
Glama

VoltPlan Wiring Diagrams

by io.github.YUZU-Hub

Generate Wiring Diagram

generate_wiring_diagram

Generate an electrical wiring diagram for campers, boats, or off-grid setups. Returns a complete schematic with batteries, chargers, protection components, and loads. Protection components (shunt, main switch, low-voltage cutoff) are auto-generated when both batteries and loads are provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loadsNoElectrical loads / consumers
formatNoOutput format: svg (recommended, renders inline) or png (base64-encoded image, may not display in all clients)svg
chargersNoChargers with their power sources
batteriesNoBatteries in the system
systemNameYesName of the electrical system (e.g. "My Camper Van")

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / chargers / items / properties / inputVoltage / description
      Previous value: -"Input voltage"New value: +"Input voltage. For shore/generator (AC) chargers use the regional mains voltage: 230 V in Europe, UK, Australia, most of Asia and Africa; 120 V in North America and Japan. For solar/wind use the panel or turbine output voltage. For alternator use the vehicle system voltage (typically 14 V)."
  2. Changed1 schema field changed
    • changedInput schema / properties / chargers / items / properties / sourceType / enum
      Previous value: -[
-  "shore",
-  "solar",
-  "wind",
-  "generator"
-]New value: +[
+  "shore",
+  "solar",
+  "wind",
+  "generator",
+  "alternator"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / format / default
      Previous value: -"png"New value: +"svg"
    • changedInput schema / properties / format / description
      Previous value: -"Output format: svg for text-based SVG, png for base64-encoded image"New value: +"Output format: svg (recommended, renders inline) or png (base64-encoded image, may not display in all clients)"
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description effectively discloses key behaviors: auto-generation of protection components when both batteries and loads are provided, and details about output format (SVG vs PNG) with rendering notes. No contradictions.

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?

Extremely concise: two sentences plus one line of behavioral detail, front-loaded with purpose and return type. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters (1 required) and no output schema, the description covers purpose, return type, output format behavior, and a key auto-generation rule. It is complete for effective use.

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%, but the description adds significant value by explaining the auto-generation rule and providing regional voltage guidance for charger input voltage, enhancing 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 generates electrical wiring diagrams for specific contexts (campers, boats, off-grid setups) and distinguishes itself from sibling calculation tools by focusing on diagram generation.

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?

Usage is clear for generating diagrams, but no explicit guidance on when not to use it or comparison with siblings is provided. However, the context makes it evident that this is for diagram output, not calculations.

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