Skip to content

Use instrument-generic futures routes in MCP 3.2.3 - #71

Merged
karlwaldman merged 1 commit into
mainfrom
codex/futures-canonical-routes-3-2-3
Aug 11, 2026
Merged

Use instrument-generic futures routes in MCP 3.2.3#71
karlwaldman merged 1 commit into
mainfrom
codex/futures-canonical-routes-3-2-3

Conversation

@karlwaldman

@karlwaldman karlwaldman commented Aug 11, 2026

Copy link
Copy Markdown
Member

Summary

  • publish instrument-generic futures slugs while preserving contract-code and legacy venue inputs
  • route both latest and curve tools through canonical generic endpoints
  • update public descriptions/live smoke and bump all release metadata to 3.2.3

Red-green proof

  • red: the old implementation failed 19 generic/code/legacy route and schema cases
  • green: 219 tests; exact latest/curve pathname matrix covers all canonical, code, and legacy spellings
  • TypeScript no-emit green; npm audit reports zero vulnerabilities
  • exact 5a10172aeb276e91a0a388f2b6316c4fc24de1f7 build: 36 tools, 46 packed/source claim surfaces, product-facts/package smokes green
  • non-root Docker smoke green with exact source provenance and live keyless stdio
  • authenticated production smoke green for generic Brent latest/curve plus the full protected live suite

Refs OilpriceAPI/oilpriceapi-api#4175

Summary by CodeRabbit

  • New Features

    • Futures tools now support canonical instrument names and aliases for Brent, WTI, gasoil, and EU carbon.
    • Added clearer account-entitlement guidance across gated tools.
    • Futures latest-data and curve checks now use standardized instrument routes.
  • Bug Fixes

    • Improved routing for legacy and canonical futures inputs.
  • Documentation

    • Updated futures examples and descriptions with generic instrument terminology.
  • Chores

    • Updated the application and server package version to 3.2.3.

@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2396e9c8-7380-4140-8e6a-94550446c7d0

📥 Commits

Reviewing files that changed from the base of the PR and between 9331d6a and 5a10172.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (9)
  • .github/workflows/live-tests.yml
  • .mcp.json
  • README.md
  • manifest.json
  • package.json
  • scripts/live-smoke.mjs
  • server.json
  • src/__tests__/index.test.ts
  • src/index.ts

📝 Walkthrough

Walkthrough

The change adds canonical futures aliases and generic endpoint slugs, updates futures metadata and smoke tests, adds account-entitlement guidance, reformats unchanged schemas and output, and increments the MCP package version to 3.2.3.

Changes

Futures routing and MCP metadata

Layer / File(s) Summary
Canonical futures routing
src/index.ts, src/__tests__/index.test.ts, scripts/live-smoke.mjs, .github/workflows/live-tests.yml, README.md
Canonical and legacy futures inputs resolve to generic slugs such as brent, wti, gasoil, and eu-carbon. Tests and smoke checks use the canonical Brent path.
Entitlement and tool metadata
src/index.ts
Tool descriptions now include account-entitlement guidance. The natural-gas-hub benchmark object uses explicit fields.
Schema and output formatting
src/index.ts, src/__tests__/index.test.ts
Well-tool schemas, request formatting, plan requests, assertions, and data-quality JSON rendering are reformatted without behavior changes.
Release version updates
src/index.ts, .mcp.json, manifest.json, package.json, server.json
MCP and package versions change from 3.2.2 to 3.2.3.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

  • OilpriceAPI/mcp-server#58: Modifies related well-tool schemas and tests, while adding separate well-tool functionality and telemetry.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the primary change: using instrument-generic futures routes in MCP version 3.2.3.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/futures-canonical-routes-3-2-3

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@karlwaldman
karlwaldman merged commit 3d80602 into main Aug 11, 2026
8 checks passed
@karlwaldman
karlwaldman deleted the codex/futures-canonical-routes-3-2-3 branch August 11, 2026 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant