Home Developers Capabilities Greatest common factor

CVP verified calculation capability

Greatest common factor Calculation Capability

Exact GCF/GCD/HCF of2–32 signed integers up to48 digits, with bounded working, strict aliases and complete method results.

Math Capability ID math.gcf version 1.0.3 CVP VERIFIED CURRENT Core

Model

Pairwise

Inputs / Outputs

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

SymbolQuantityUnitRole
values——input / output
numbers——input
numsInput——input
value——output
count——output
binary_formula——output
methods——output
work——output
max_digits——output

Trusted Math contract

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

FieldDeclaration
numeric_domaininteger
exactnessexact
algorithmEuclidean algorithm (gcd of an integer list)
valid_domain2–32 signed integers of at most48 digits; safe numeric JSON or decimal strings; matching ordered aliases; not all zero
singularity_policyMISSING_REQUIRED_INPUT for empty; NEED_TWO_NUMBERS for one; TOO_MANY_VALUES over32; UNDEFINED for all zeros; reject unsafe numeric integers and malformed text
branch_policynot applicable — integer domain
tolerancenot applicable — exact integer identity
convergencenot applicable — non-iterative Euclidean / combinatorial
conditioningnot applicable — not a floating matrix
roundingnone — BigInt / exact integer
overflowcoded error or stringified BigInt when exceeding JSON number
reproducibilitydeterministic exact integer + Capability@Version
independent_oracleEvidence 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.

GCF(8,12,20)=4; GCF(0,0,5)=5; GCF(9007199254740993, 3)=3

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Core 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 · Core assurance· View Manifest · CVP overview · Specification
Assurance
Core
Declared partition coverage
PASS · 8/8 declared partitions (gcf, zero, negative, beyond-safe-integer, multi-input-fold, method-unavailable, xcal, invalid-domain)
Calculation version
1.0.3
Verification
20/20 calculation tests · 6/6 legacy golden · 7/7 legacy boundary · 7/7 legacy property
Production surface contract
6/6
Versions
Calculation 1.0.3 · CVP protocol 1.0.0-proposed · Evidence 2026-10-21.gcf-complete-contract-v4
Verification revision
2026-10-21.gcf-complete-contract-v4 · 3/3 property · digest 9af66f58265f
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
10/10 golden · 7/7 CVP boundary · 5/5 invalid · 3/3 property · 1/1 metamorphic · 2/2 cross-interface · 5/5 cross-calculator · 6/6 CVP contract
Supplemental domain review
Not performed
Named expert review
Not performed
Version lock
Supported (409 VERSION_MISMATCH)
Artifact consistency
Build verified · 1.0.3 (workspace artifacts agree)
Review-policy tier
Engine tested — catalog token engine_tested; supplemental; not CVP status
This calculator CURRENT · Public schema 1.0.3 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/gcf' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"values":[8,12,20]},"calculation_version":"1.0.3"}'

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

Full REST contract: REST API docs.

Tool id
gcf
Engine
gcf
REST
POST /api/v1/calc/gcf
MCP
execute_calculation with capability_id: "math.gcf"
Agent input schema
Canonical (MCP / Agent)
REST input schema
Compatibility (tol[] / tol1…)
Output schema
JSON Schema (latest)
Versioned input schema
Immutable pin (1.0.3)
Versioned output schema
Immutable pin (1.0.3)

References

Human-readable sources plus CVP reference evidence classes.

Sources

Derived identities

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.gcf"},"_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.0.3) when the result must stay reproducible.

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