Home Developers Capabilities Battery runtime

CVP verified calculation capability

Battery runtime Calculation Capability

Estimate constant-load battery runtime from capacity, voltage, load (W load-side or A battery-side), DoD, and load-side efficiency (watts mode); optional u_* compose expanded uncertainty on t_h via Uncertainty Engine.

Electrical Capability ID electrical.battery_runtime version 1.2.1 CVP VERIFIED CURRENT Engineering

Model

Usable energy (watts mode)

Modes: watts · amps

Inputs / Outputs

Canonical symbols for this capability. Agent schemas remain the contract.

SymbolQuantityUnitRole
capacity_AhBattery capacity in amp-hoursinput / output
capacity_mAhBattery capacity in mAh; Ah = mAh/1000input / output
VNominal pack voltageinput / output
PConstant delivered load-side powerWinput
dodPlanning depth of discharge ininput / output
etaLoad-side delivery efficiency ininput / output
u_capacity_AhOptional standard uncertainty of capacity_Ahinput / output
uOptional standard uncertainty of VVinput / output
u_POptional standard uncertainty of P_WWinput
u_dodOptional standard uncertainty of dodinput / output
u_etaOptional standard uncertainty of etainput / output
uncertainty_kCoverage factor for expanded U on t_h; default 2 when any u_* is setinput / output
confidenceCoverage probability instead of uncertainty_kinput / output
IConstant battery-side discharge currentAinput
u_IOptional standard uncertainty of I_AAinput
t_hEstimated runtimeoutput
t_dEstimated runtimeoutput
E_WhUsable energy in Whoutput
uncertaintyPresent when any u_* is provided; UncertaintySummary via engineeringoutput

Assumptions / Validity

Declared scope for this capability. Do not use it outside this domain.

Assumptions

Example

One numerical check. The calculator page holds worked steps and FAQ.

10 Ah, 12 V, 20 W, DoD 0.8, η 0.9 → t_h = 4.32, E_Wh = 86.4

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance. Computational verification is defined by CVP. Supplemental domain review (internal) and named expert review are defined by the Review policy and do not by themselves determine CVP conformance.

CVP
CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance· View Manifest · CVP overview · Specification
Assurance
Engineering
Declared partition coverage
PASS · 3/3 declared partitions (watts, amps, invalid-domain)
Calculation version
1.2.1
Verification
25/25 calculation tests · 5/5 legacy golden · 10/10 legacy boundary · 10/10 legacy property
Production surface contract
8/8
Versions
Calculation 1.2.1 · CVP protocol 1.0.0-proposed · Evidence 2026-09-11.schema-coverage-u
Verification revision
2026-09-11.schema-coverage-u · 10/10 property · digest 058cf03cbe19
Reference
O1 model · O2 expected_values · O2 numerical_behavior
Interfaces
PASS · UI (SSR) / REST / MCP
ui-ssr is query-result HTML, not a live browser session.
CVP suite
3/3 golden · 9/9 CVP boundary · 7/7 invalid · 10/10 property · 1/1 cross-interface · 6/6 CVP contract
Supplemental domain review
Internal · Pass · electrical-engineer
Named expert review
Not performed
Version lock
Supported (409 VERSION_MISMATCH)
Artifact consistency
Build verified · 1.2.1 (workspace artifacts agree)
Review-policy tier
Internally reviewed — catalog token internally_reviewed; supplemental; not CVP status
This calculator CURRENT · Public schema 1.2.1 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

Call this capability

Human page, REST, and MCP share the same engine and calculation_version. Build verified hashes workspace artifacts only. After deploy, attest:production GETs canonical URLs twice — the public/cached view an Agent actually hits, and origin — including every /capabilities/{id} HTML page. Public Capability HTML version must match catalog before production attestation passes. Live Trust rows above fetch /.well-known/calculatorx-production-attestation.json and the output schema const. Build hashes: release integrity. That proves currently published page / engine / schema / evidence / MCP agree — not that a historical version is independently immutable. Reference Calculation Standard — Production surface contract 8/8.

curl -sS -X POST 'https://www.calculatorx.com/api/v1/calc/battery-runtime' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"mode":"watts","capacity_Ah":10,"V":12,"P_W":20,"dod":1,"eta":1},"calculation_version":"1.2.1"}'

POST /api/v1/calc/battery-runtime. This is a POST calculate endpoint — do not GET it.

Full REST contract: REST API docs.

Tool id
battery-runtime
Engine
battery-runtime
REST
POST /api/v1/calc/battery-runtime
MCP
execute_calculation with capability_id: "electrical.battery_runtime"
Agent input schema
Canonical (MCP / Agent)
Output schema
JSON Schema (latest)
Versioned input schema
Immutable pin (1.2.1)
Versioned output schema
Immutable pin (1.2.1)

Operations

Declared calculation modes for this capability.

References

Human-readable sources plus CVP reference evidence classes.

Sources

Reference evidence classes: O1 model · O2 expected_values · O2 numerical_behavior

Try with an agent

Inspect, then execute. Same engine as REST and the human calculator.

curl -sS -X POST 'https://www.calculatorx.com/mcp' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/call' \
  -H 'Mcp-Name: inspect_capability' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"inspect_capability","arguments":{"capability_id":"electrical.battery_runtime"},"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"calculatorx-docs-example","version":"1.0.0"},"io.modelcontextprotocol/clientCapabilities":{}}}}'

Pin calculation_version (1.2.1) when the result must stay reproducible.

Inspect the trust tier and required assurance level before execution. Full protocol notes: MCP docs.