Skip to main content
Glama
YUZU-Hub

wiring-diagram-mcp

by YUZU-Hub

Charging Time Calculator

calculate_charging_time

Calculate charging time for a battery bank from any state of charge to target, accounting for bulk and absorption phases. Supports solar, shore power, or alternator inputs.

Instructions

Estimate how long it takes to charge a battery bank from a given state of charge to a target level. Accounts for the bulk charging phase (constant current, up to ~80% SoC) and the slower absorption phase (tapering current, 80-100% SoC). Works for any charging source: solar, shore power, alternator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batteryCapacityAhYesTotal battery bank capacity in amp-hours
batteryVoltageYesBattery bank voltage (e.g. 12, 24, 48)
currentStateOfChargePercentYesCurrent state of charge in percent (e.g. 20 for 20%)
targetStateOfChargePercentNoTarget state of charge in percent (default: 100)
chargePowerWattsYesCharger output power in watts
chargeCurrentAmpsNoMaximum charge current in amps (if limited by the charger or battery BMS). If omitted, calculated from power and voltage.
Behavior3/5

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

The description discloses that it accounts for bulk and absorption phases, but lacks details on limitations (e.g., battery chemistry, temperature effects, assumed charge profile). With no annotations, the description carries full burden but is not fully transparent.

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: one for purpose, one for behavioral detail and scope. No unnecessary words, front-loaded with key information.

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

Completeness3/5

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

The description covers the core functionality and scope, but lacks details on output format, edge cases, or assumptions. For a tool with 6 parameters and no output schema, it is adequate but not complete.

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 parameters are already well-documented. The description adds context about charging phases but does not enhance parameter meaning beyond 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 estimates charging time for a battery bank from a given state of charge to a target level, using specific verbs and resources. It distinguishes from sibling tools focused on battery sizing, solar sizing, etc.

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?

The description mentions it works for any charging source (solar, shore, alternator) and accounts for charging phases, giving context on when to use. However, it does not explicitly state when not to use or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YUZU-Hub/wiring-diagram-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server