Skip to main content
Glama
log-wade

datacenter-mcp-server

by log-wade

UPS & Battery Sizing Calculator

dc_ups_battery_sizing
Read-onlyIdempotent

Calculate UPS and battery plant sizing for data centers, including redundancy configurations, runtime, floor space, and 10-year TCO comparison between VRLA and lithium-ion.

Instructions

Size UPS systems and battery plants for mission-critical data center facilities. Calculates UPS module count, battery string sizing, floor space, structural load, and 10-year Total Cost of Ownership comparing VRLA vs Lithium-Ion batteries.

Supports all standard redundancy configurations (N, N+1, 2N, 2N+1) and both battery technologies with lifecycle cost analysis including replacement cycles.

Args:

  • critical_load_kw (number): Critical IT load in kW

  • redundancy (string): "N", "N+1", "2N", or "2N+1"

  • runtime_minutes (number): Required battery runtime (5, 10, 15, or 30)

  • battery_type (string): "VRLA" or "lithium_ion"

  • ups_efficiency (number): UPS efficiency 0.8-0.99 (default: 0.96)

  • growth_factor (number): Design growth margin 1.0-2.0 (default: 1.2)

Returns UPS module sizing, battery string count, energy capacity, floor space requirements, weight estimates, 10-year TCO comparison, and recommendations.

Examples:

  • "Size a 2N UPS with 15 min lithium batteries for 2 MW" -> critical_load_kw: 2000, redundancy: "2N", runtime_minutes: 15, battery_type: "lithium_ion"

  • "Compare VRLA vs lithium for 500 kW N+1" -> critical_load_kw: 500, redundancy: "N+1", runtime_minutes: 10, battery_type: "VRLA"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
redundancyYesUPS redundancy configuration: N (no redundancy), N+1 (single fault tolerance), 2N (parallel dual), 2N+1 (enhanced parallel)
aging_factorNoEnd-of-life aging factor per IEEE 485 practice (default: 1.25 — batteries must meet load at end of life)
battery_typeYesBattery technology: VRLA (traditional lead-acid), lithium_ion (LiFePO4 modern)
growth_factorNoDesign growth factor for future expansion (default: 1.2 = 20% growth margin)
ups_efficiencyNoUPS rectifier/inverter efficiency at rated load (default: 0.96 = 96%)
runtime_minutesYesRequired UPS battery runtime in minutes (typical: 5-15 min for generator start, 30+ for extended runtime)
critical_load_kwYesCritical IT load requiring UPS protection in kilowatts
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which the description does not contradict. The description adds useful context about what the tool calculates (including lifecycle cost analysis with replacement cycles) and that it returns recommendations, which goes beyond the bare safety annotations.

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?

The description is well-structured with a clear opening purpose, followed by Args, Returns, and Examples sections. It is front-loaded and every major section earns its place, though the Args list largely duplicates schema descriptions, making it slightly longer than necessary.

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?

Given that there is no output schema, the description adequately explains what the tool returns (UPS module sizing, battery string count, floor space, weight, TCO, recommendations) and covers supported configurations and battery types. The examples further clarify expected parameter usage, making the tool fully usable without external documentation.

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

Parameters2/5

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

Although schema coverage is 100%, the description's Args section adds little beyond the schema and actually introduces a misleading restriction: 'runtime_minutes (5, 10, 15, or 30)' contradicts the schema's range of 5-120. The examples are helpful for mapping natural language to parameters, but the inaccuracy lowers the value added.

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's purpose with specific verbs ('Size', 'Calculates') and a defined resource ('UPS systems and battery plants'). It lists concrete outputs (module count, battery string sizing, TCO) and explicitly distinguishes itself from sibling tools like cooling load calculators or generic power redundancy analysis.

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 establishes clear usage context by specifying the domain (mission-critical data centers), supported redundancy configurations, battery technologies, and typical runtime values. It does not name alternatives or explicit exclusions, but the focus on UPS/battery sizing is unmistakable compared to siblings.

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/log-wade/datacenter-mcp-server'

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