Verified calculation capability

eV to Volts Calculation Capability

Relate electronvolt energy to electric potential difference through E = qV using charge magnitude and the exact SI elementary charge. · Electrical

Capability ID electrical.ev_voltage · version 1.3.0

Open calculator REST API MCP Evidence Evidence JSON CVP Manifest Review policy

Model

eV → V (elementary charge)

eV → V (elementary charge): V = E(eV) ÷ Q(e)
eV → V (coulombs): V = 1.602176634×10⁻¹⁹ × E(eV) ÷ Q(C)
V → eV (elementary charge): E(eV) = V × Q(e)
V → eV (coulombs): E(eV) = V × Q(C) ÷ 1.602176634×10⁻¹⁹

Solve modes: ev-v-e · ev-v-c · v-ev-e · v-ev-c

Inputs / Outputs

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

Symbol	Quantity	Unit	Role
`direction`	Semantic alias for mode when mode is omitted	—	input / output
`energy_eV`	Energy in electronvolts (energy→voltage)	—	input / output
`voltage`	Potential difference in volts (voltage→energy)	V	input / output
`charge_value`	Charge magnitude in elementary-charge units or coulombs	—	input / output
`charge_unit`	Used with direction when mode is omitted	—	input / output
`charge_convention`	Only magnitude is supported	—	input / output
`a`	Legacy: energy_eV or voltage_V depending on mode	—	input
`b`	Legacy alias for charge_value	—	input
`Q`	—	—	input
`value`	Primary result: volts or eV	—	output
`unit`	—	—	output
`elementary_charge`	Exact SI e = 1.602176634e-19 C	°C	output

Assumptions / Validity

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

Assumptions

Elementary charge e = 1.602176634×10⁻¹⁹ C exactly (SI defining constant; no uncertainty)
Uses the electrostatic energy–potential relation E = qV
Q(e) and Q(C) denote charge magnitude; sign and direction of the potential difference are not modeled

Example

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

25 eV ÷ 10 e = 2.5 V

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 · 5/5 declared partitions (ev-v-e, ev-v-c, v-ev-e, v-ev-c, invalid-domain)
Calculation version: 1.3.0
Verification: 21/21 calculation tests · 12/12 legacy golden · 5/5 legacy boundary · 4/4 legacy property
Production surface contract: 3/3
Versions: Calculation 1.3.0 · CVP protocol 1.0.0-proposed · Evidence 2026-09-14.si-exact-e-zero-charge
Verification revision: 2026-09-14.si-exact-e-zero-charge · 2/2 property · digest 99c55c4d8029
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: 6/6 golden · 8/8 CVP boundary · 11/11 invalid · 2/2 property · 3/3 metamorphic · 1/1 round-trip · 3/3 cross-interface · 3/3 CVP contract
Supplemental domain review: Not performed
Named expert review: Not performed
Version lock: Supported (409 VERSION_MISMATCH)
Artifact consistency: Build verified · 1.3.0 (workspace artifacts agree)
Review-policy tier: Engine tested — catalog token engine_tested; supplemental; not CVP status

This calculator CURRENT · Public schema 1.3.0 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 3/3.

Tool id: ev-to-volts
Engine: ev-voltage
REST: POST /api/v1/calc/ev-to-volts
MCP: execute_calculation with capability_id: "electrical.ev_voltage"
Agent input schema: Canonical (MCP / Agent)
Output schema: JSON Schema (latest)
Versioned input schema: Immutable pin (1.3.0)
Versioned output schema: Immutable pin (1.3.0)

Operations

Declared calculation modes for this capability.

ev-v-e
ev-v-c
v-ev-e
v-ev-c

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 this capability via same-origin MCP, then call execute_calculation.

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.ev_voltage"}}}'

Inspect the trust tier and required assurance level before execution. Pin calculation_version (1.3.0) when reproducibility matters. Full protocol notes: MCP docs.