Verified calculation capability

Coordinate geometry Calculation Capability

Distance, midpoint, and slope of two points in the plane. Slope is not share-key m. · Math · Geometry

Capability ID math.geometry.coordinate · version 1.0.0

Open calculator REST API MCP Evidence Evidence JSON Review policy

Model

Distance

Distance: d = √((x₂−x₁)²+(y₂−y₁)²)
Midpoint: M = ((x₁+x₂)/2, (y₁+y₂)/2)
Slope: slope = (y₂−y₁)/(x₂−x₁)

Solve modes: distance · midpoint · slope

Inputs / Outputs

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

Symbol	Quantity	Unit	Role
`x1`	—	—	input
`y1`	—	—	input
`x2`	—	—	input
`y2`	—	—	input
`distance`	—	—	output
`mx`	—	—	output
`my`	—	—	output
`slope`	—	—	output
`vertical`	—	—	output
`intercept`	—	—	output

Assumptions / Validity

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

Assumptions

Euclidean plane
Not 3-D / spherical

Example

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

distance (0,0)(3,4) → 5

Open this example in the calculator

Trust

Review-policy: engine tested — automated tests, sources, version lock, and evidence published. Supplemental to CVP; not Domain Expert Review. See CVP and Review policy.

Tier: Engine tested — catalog token engine_tested
Calculation version: 1.0.0
Evidence tests: 10/10 calculation tests · golden 4/4 · boundary 1/1 · property 5/5
Engine tested: Yes
Source checked: Yes
Supplemental domain review: Not performed
Named expert review: Not performed
Version lock: Supported (409 VERSION_MISMATCH)
Artifact consistency: Build verified · 1.0.0 (workspace artifacts agree)

Production attestation: Embedded snapshot: unpublished · Build schema 1.0.0 ready · Semantic contract ✓ · Attestation report not published on origin · Live production status PASS (0 stale; 164 CURRENT) @ 2026-09-16T06:44:24.909Z
Semantic contract: PASS
Evidence attested at: 2026-09-16T06:44:24.203Z
Last production check: 2026-09-16T06:44:24.203Z
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: coordinate-geometry
Engine: coordinate-geometry
REST: POST /api/v1/calc/coordinate-geometry
MCP: execute_calculation with capability_id: "math.geometry.coordinate"
Agent input schema: Canonical (MCP / Agent)
Output schema: JSON Schema (latest)
Versioned input schema: Immutable pin (1.0.0)
Versioned output schema: Immutable pin (1.0.0)

References

Human-readable sources plus CVP reference evidence classes.

Sources

ISO 80000-2:2019 Quantities and units — Mathematics

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":"math.geometry.coordinate"}}}'

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