Home Developers Capabilities Complex numbers

CVP verified calculation capability

Complex numbers Calculation Capability

Rectangular and polar complex arithmetic, integer powers, nth roots, and Euler form. Not a CAS.

Math Capability ID math.complex version 1.1.0 CVP VERIFIED CURRENT Core

Model

Modulus

Modes: add · sub · mul · div · rect to polar · polar to rect · conjugate · modulus · power · root · euler

Inputs / Outputs

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

SymbolQuantityUnitRole
re——input / output
im——input / output
re2——input
im2——input
r——input / output
arg_degArgument in degrees, atan2 convention—input / output
nInteger exponent for power; n≥2 for roots—input / output
from——input
euler——output
roots——output

Trusted Math contract

Inspectable numeric contract for this Capability@Version. Not a rewrite of the engine.

FieldDeclaration
numeric_domaincomplex
exactnessfloat64
algorithmrectangular ± polar arithmetic; De Moivre integer powers / nth roots; Euler form
valid_domainfinite re, im; r ≥ 0; integer n for powers/roots
singularity_policyDIVISION_BY_ZERO on 0+0i divisor
branch_policyarg = atan2 in (−180°, 180°]; principal nth-root then rotate
tolerancenot applicable — IEEE-754; polar snap as published
convergencenot applicable — non-iterative
conditioningnot applicable — not a matrix κ product
roundingieee754_round_ties_to_even
overflowieee754_nonfinite_or_coded_error
reproducibilitydeterministic + Capability@Version
independent_oraclecvp:math.complex O2 / Evidence published cases
golden_vectorsEvidence golden + boundary + property (and published_reference_case when listed)

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.

mode=add re=1 im=2 re2=3 im2=4 → 4+6i

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Core assurance · all published modes. 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 · Core assurance · all published modes· View Manifest · CVP overview · Specification
Verified scope
all published modes
Assurance
Core
Declared partition coverage
PASS · 12/12 declared partitions (add, sub, mul, div, rect-to-polar, polar-to-rect, conjugate, modulus, power, root, euler, invalid-domain)
Calculation version
1.1.0
Verification
18/18 calculation tests · 6/6 legacy golden · 4/4 legacy boundary · 8/8 legacy property
Production surface contract
5/5
Versions
Calculation 1.1.0 · CVP protocol 1.0.0-proposed · Evidence 2026-09-22.vector-la-cvp
Verification revision
2026-09-22.vector-la-cvp · 3/3 property · digest 403fe3cb25d5
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. Error-path engine·REST·MCP 1/1 (status, code, calculation_version). SSR compared on URL-canonical requested calculations; empty query is idle (not an error) and JSON-typed object/array inputs are REST/MCP-only.
CVP suite
11/11 golden · 5/5 CVP boundary · 9/9 invalid · 3/3 property · 5/5 cross-interface · 2/2 cross-calculator · 5/5 CVP contract
Supplemental domain review
Not performed
Named expert review
Not performed
Version lock
Supported (409 VERSION_MISMATCH)
Artifact consistency
Build verified · 1.1.0 (workspace artifacts agree)
Review-policy tier
Engine tested — catalog token engine_tested; supplemental; not CVP status
This calculator CURRENT · Public schema 1.1.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 5/5.

curl -sS -X POST 'https://www.calculatorx.com/api/v1/calc/complex' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"mode":"add","re":1,"im":2,"re2":3,"im2":4},"calculation_version":"1.1.0"}'

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

Full REST contract: REST API docs.

Tool id
complex
Engine
complex
REST
POST /api/v1/calc/complex
MCP
execute_calculation with capability_id: "math.complex"
Agent input schema
Canonical (MCP / Agent)
Output schema
JSON Schema (latest)
Versioned input schema
Immutable pin (1.1.0)
Versioned output schema
Immutable pin (1.1.0)

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":"math.complex"},"_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.1.0) when the result must stay reproducible.

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