Verified calculation capability

One-dimensional optimization Calculation Capability

Minimize a polynomial, sin, or exp on [a, b] by golden-section search or Brent. Not multivariate, not maximization, not CAS. · Math · Numerical

Capability ID math.numerical.optimize_1d · version 1.0.0

Open calculator REST API MCP Evidence Evidence JSON Review policy

Model

Golden

Golden: c = b − φ̂(b−a), d = a + φ̂(b−a)
Brent: golden section + inverse parabolic interpolation

Inputs / Outputs

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

Symbol	Quantity	Unit	Role
`method`	—	—	input / output
`integrand`	—	—	input / output
`a`	acceleration	—	input / output
`b`	—	—	input / output
`tol`	—	—	input
`coeffs`	c0,c1,…,cn constant first	—	input
`xmin`	—	—	output
`fmin`	—	—	output
`exact_xmin`	—	—	output
`exact_fmin`	—	—	output
`abs_err_x`	—	—	output
`n_eval`	—	—	output

Assumptions / Validity

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

Assumptions

Minimize only; f treated as unimodal on [a, b]
Not multivariate and not CAS
Polynomial degree ≤ 8

Example

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

golden poly 0,0,1 on [-1,2] → xmin=0

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: 11/11 calculation tests · golden 3/3 · boundary 2/2 · property 6/6
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 STALE (1 capability; 163 remain CURRENT) @ 2026-09-19T00:00:17.039Z
Semantic contract: PASS
Evidence attested at: 2026-09-18T21:41:55.460Z
Last production check: 2026-09-18T21:41:55.460Z
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 2/2.

Tool id: one-dimensional-optimization
Engine: one-dimensional-optimization
REST: POST /api/v1/calc/one-dimensional-optimization
MCP: execute_calculation with capability_id: "math.numerical.optimize_1d"
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.numerical.optimize_1d"}}}'

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