CVP verified calculation capability

Voltage divider Calculation Capability

Solve unloaded two-resistor divider networks from exactly three of Vin, R1, R2, Vout; also returns series current, resistor power, divider ratio, and Thevenin output resistance Rth.

Electrical Capability ID electrical.voltage_divider version 1.5.1 CVP VERIFIED CURRENT Engineering

Model

Output voltage

Output voltage: Vout = Vin × R2 / (R1 + R2)
Solve R2: R2 = R1 × Vout / (Vin − Vout)
Solve R1: R1 = R2 × (Vin − Vout) / Vout
Solve Vin: Vin = Vout × (R1 + R2) / R2
Current: I = Vin / (R1 + R2)
Divider ratio: k = R2 / (R1 + R2)
Output resistance: Rth = R1 ∥ R2 = R1 R2 / (R1 + R2)

Inputs / Outputs

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

Symbol	Quantity	Unit	Role
`Vin`	Source voltage	—	output
`R1`	Upper resistor	—	output
`R2`	Lower resistor	—	output
`Vout`	Tap voltage across R2	—	output
`I`	Series current	—	output
`P1`	Power in R1	—	output
`P2`	Power in R2	—	output
`Ptotal`	Total divider dissipation	—	output
`ratio`	Unloaded divider ratio R2 /	—	output
`Rth`	Thevenin output resistance R1∥R2	—	output

Assumptions / Validity

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

Assumptions

No load on Vout
DC / resistive
R1 from Vin to tap; R2 from tap to ground

Example

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

5 V, 1 kΩ, 2 kΩ → Vout = 3.333 V · I ≈ 1.667 mA · Rth ≈ 667 Ω

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 (solve-vout, solve-r, invalid-domain)
Calculation version: 1.5.1
Verification: 28/28 calculation tests · 9/9 legacy golden · 8/8 legacy boundary · 11/11 legacy property
Production surface contract: 6/6
Versions: Calculation 1.5.1 · CVP protocol 1.0.0-proposed
CVP identity: 11/11 property · digest 634843a750b6
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 · 8/8 CVP boundary · 8/8 invalid · 11/11 property · 1/1 cross-interface · 4/4 CVP contract
Supplemental domain review: Not performed
Named expert review: Not performed
Version lock: Supported (409 VERSION_MISMATCH)
Artifact consistency: Build verified · 1.5.1 (workspace artifacts agree)
Review-policy tier: Engine tested — catalog token engine_tested; supplemental; not CVP status

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

curl -sS -X POST 'https://www.calculatorx.com/api/v1/calc/voltage-divider' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"Vin":5,"R1":1000,"R2":2000},"calculation_version":"1.5.1"}'

{
  "inputs": {
    "Vin": 5,
    "R1": 1000,
    "R2": 2000
  },
  "calculation_version": "1.5.1"
}

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

Full REST contract: REST API docs.

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

Operations

Declared calculation modes for this capability.

solve-Vout
solve-R2
solve-R1
solve-Vin

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.voltage_divider"},"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"calculatorx-docs-example","version":"1.0.0"},"io.modelcontextprotocol/clientCapabilities":{}}}}'

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: execute_calculation' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"execute_calculation","arguments":{"capability_id":"electrical.voltage_divider","inputs":{"Vin":5,"R1":1000,"R2":2000},"calculation_version":"1.5.1"},"_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.5.1) when the result must stay reproducible.

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