Skip to main content
Glama
Sign In

VoltPlan Wiring Diagrams

by io.github.YUZU-Hub
OverviewDiscussionsAdmin

Generate Wiring Diagram

generate_wiring_diagram
Read-onlyIdempotent

Generate an electrical wiring diagram for campers, boats, or off-grid setups. Returns the schematic as an image (batteries, chargers, protection components, loads) and a link that opens it in the VoltPlan editor to refine, save and turn into a shopping list. Protection components (shunt, main switch, low-voltage cutoff) are auto-generated when both batteries and loads are provided. Show the user the editor link.

Input Schema

NameRequiredDescriptionDefault
loadsNoElectrical loads / consumers
formatNopng (default): an image the client displays. svg: SVG markup as text, without component icons, for clients that save or post-process files.png
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.

  1. Changed13 schema fields changed
    • changedInput schema / properties / batteries / items / properties / capacityAh / description
      Previous value: -"Capacity in amp-hours"New value: +"Capacity in amp-hours. Give this or energyWh."
    • changedInput schema / properties / batteries / items / properties / energyWh / description
      Previous value: -"Energy in watt-hours"New value: +"Energy in watt-hours. Calculated from capacityAh × voltage when omitted."
    • changedInput schema / properties / batteries / items / properties / voltage / description
      Previous value: -"Nominal voltage (e.g. 12)"New value: +"Nominal voltage (e.g. 12, or 12.8 for LiFePO4)"
    • changedInput schema / properties / batteries / items / required
      Previous value: -[
-  "name",
-  "voltage",
-  "capacityAh",
-  "energyWh"
-]New value: +[
+  "name",
+  "voltage"
+]
    • changedInput schema / properties / chargers / items / properties / outputVoltage / description
      Previous value: -"Output voltage"New value: +"Output voltage. Defaults to the first battery's voltage (or 12 V)."
    • changedInput schema / properties / chargers / items / required
      Previous value: -[
-  "name",
-  "inputVoltage",
-  "outputVoltage",
-  "power"
-]New value: +[
+  "name",
+  "inputVoltage",
+  "power"
+]
    • changedInput schema / properties / format / default
      Previous value: -"svg"New value: +"png"
    • changedInput schema / properties / format / description
      Previous value: -"Output format: svg (recommended, renders inline) or png (base64-encoded image, may not display in all clients)"New value: +"png (default): an image the client displays. svg: SVG markup as text, without component icons, for clients that save or post-process files."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "svg",
-  "png"
-]New value: +[
+  "png",
+  "svg"
+]
    • changedInput schema / properties / loads / items / properties / current / description
      Previous value: -"Current draw in amps"New value: +"Current draw in amps. Calculated from power / voltage when omitted."
    • changedInput schema / properties / loads / items / properties / power / description
      Previous value: -"Power consumption in watts"New value: +"Power consumption in watts. Give this or current."
    • changedInput schema / properties / loads / items / properties / voltage / description
      Previous value: -"Operating voltage"New value: +"Operating voltage. Defaults to the first battery's voltage (or 12 V)."
    • changedInput schema / properties / loads / items / required
      Previous value: -[
-  "name",
-  "power",
-  "voltage",
-  "current"
-]New value: +[
+  "name"
+]
  2. 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)."
  3. 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"
+]
  4. 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)"
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description still adds real value beyond that: it discloses the return payload (schematic image plus editor link), the conditional auto-generation of shunt/main switch/low-voltage cutoff, and a required UX action (show the link).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the purpose and output, then the conditional behavior, then the actionable instruction. Each sentence carries information; only the parenthetical component list is mildly redundant with the schema.

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?

With no output schema, the description takes on the burden of explaining return values and does so precisely (image plus editor link, plus the svg-format alternative documented in the schema). Combined with the read-only annotations, an agent has everything needed to call and use this tool correctly.

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 the parameters are fully documented in structured form. The description mentions the key input categories (batteries, chargers, loads, protection components) but adds no syntax or format guidance beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource ('Generate an electrical wiring diagram') and scopes the domain to campers, boats, and off-grid setups. This clearly separates it from the sibling calculate_* tools, which compute values rather than produce diagrams.

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?

Implicit context for use is clear (vehicle/marine/off-grid system diagrams), and the description states a concrete trigger condition for auto-generating protection components ('when both batteries and loads are provided'). It also gives the agent a follow-up instruction to show the editor link. It stops short of naming when not to use it or pointing at a specific alternative sibling.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources