Skip to content

feat(mcp)!: get_container returns the full event timeline; remove get_container_transport_events - #515

Merged
alosec merged 7 commits into
mainfrom
alosec/get-container-full-events
Nov 13, 2026
Merged

alosec merged 7 commits into
mainfrom
alosec/get-container-full-events

Conversation

@alosec

@alosec alosec commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Why

get_container with transport_events summarized events as a count plus the single event with the largest timestamp. Future estimates always outrank actual events, and when a carrier reports arrival estimates on two voyages, the furthest-out one wins. Agents then quote that date as the ETA without seeing the current estimate.

Even with every event visible, carriers report several estimates for the same arrival. Sorted by estimated date, the last one listed is not the current one, and nothing said which was reported most recently.

What

  • Transport events always load in get_container. include: ["transport_events"] is still accepted but changes nothing.
  • events.timeline lists every event oldest first, with vessel, voyage, location and invalidated_at.
  • Timeline events carry reported_at (the event's created_at). The get_container description says the current ETA is the estimate with the latest reported_at.
  • events.latest_event is removed. events.count and events.rail_events_count still count active events.
  • The steering filter keeps reported values at events.timeline[n].value.
  • Tool descriptions, server instructions and docs/mcp/home.mdx updated; tools/list and instructions snapshots regenerated.

Removes get_container_transport_events

get_container returns the same timeline, so the second tool is gone (registry, server, feature map, tests, docs, changelog). The timeline formatter moves to lib/event-timeline.ts. Breaking for MCP clients that call it; the replacement is get_container → events.timeline. The default tools/list goes from 31 to 30.

The directory listing files (chatgpt-app-submission.json, claude-connector-submission.json) drop the tool in a separate commit. The submitted listings themselves are unchanged until they are resubmitted.

Verification

  • vp run check, vp run build, npm run agent-verify pass.
  • MCP tests: 987 pass, including a regression test with two arrival estimates on different voyages and their reported_at.
  • Agent eval on a frozen data snapshot, one container whose carrier estimates span three voyages (3 trials each, model judge):
MCP Pass What the agent said
main 0/3 No ETA; the summary's latest_event was a stale estimate months out
full timeline 0/3 Right voyage, but the last-listed estimate, not the latest reported
full timeline + reported_at 3/3 The current estimate

🤖 Generated with Claude Code

alosec and others added 2 commits November 13, 2026 14:58
get_container reduced transport events to a count and the event with the
largest timestamp. Future estimates outrank actual events, and a far-out
estimate on another voyage outranked the current ETA, so agents quoted the
wrong arrival date unless they also called get_container_transport_events.

Transport events now always load, and events.timeline lists every event
oldest first in the same shape as get_container_transport_events
(vessel, voyage, location, invalidated_at). latest_event is removed.
Passing transport_events in include is accepted and changes nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
terminal49 🟢 Ready View Preview Nov 13, 2026, 9:24 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@vercel

vercel Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
api Ready Ready Preview Nov 13, 2026 9:24pm UTC

Request Review

@github-actions

Copy link
Copy Markdown
Contributor

Shadow risk calibration

Signal Result Authority
Path classifier risk:high Deterministic advisory policy
heuristic fallback risk-shadow:high Shadow only

Calibration result: agreement.

Shadow risk never blocks or enables merge. Keep it in observation mode until roughly 50 pull requests have human-reviewed labels, then calibrate before considering any policy use.

@github-actions github-actions Bot added the risk:unknown Advisory evidence unavailable or changed; no merge permission label Nov 13, 2026
@github-actions github-actions Bot added risk:high Advisory path risk; current-head human review needed and removed risk:unknown Advisory evidence unavailable or changed; no merge permission labels Nov 13, 2026
alosec and others added 2 commits November 13, 2026 15:15
Carriers report several estimates for the same arrival. Sorted by estimated
date, the last one listed is not the current one; without the report time the
model picked it. reported_at (the event's created_at) lets the latest report
win, and the get_container description says so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission and removed risk:high Advisory path risk; current-head human review needed labels Nov 13, 2026
@github-actions github-actions Bot added risk:high Advisory path risk; current-head human review needed and removed risk:unknown Advisory evidence unavailable or changed; no merge permission labels Nov 13, 2026
alosec and others added 3 commits November 13, 2026 15:24
get_container returns the same timeline in events.timeline, so the second
tool only gave agents two ways to read a container and a reason to stop at
the first. The timeline formatter moves to lib/event-timeline.ts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alosec alosec changed the title fix(mcp): get_container always returns the full event timeline feat(mcp)!: get_container returns the full event timeline; remove get_container_transport_events Nov 13, 2026
@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission and removed risk:high Advisory path risk; current-head human review needed labels Nov 13, 2026
@github-actions github-actions Bot added risk:high Advisory path risk; current-head human review needed and removed risk:unknown Advisory evidence unavailable or changed; no merge permission labels Nov 13, 2026
@alosec
alosec marked this pull request as ready for review November 13, 2026 21:26
@alosec
alosec merged commit 2d3a856 into main Nov 13, 2026
33 checks passed
@alosec
alosec deleted the alosec/get-container-full-events branch November 13, 2026 21:26
@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission and removed risk:high Advisory path risk; current-head human review needed labels Nov 13, 2026

This branch was successfully deployed

2 active deployments
Preview — 5bfe7039 Deployed Nov 13, 2026 by vercel[bot]
staging - docs — 5bfe7039 Deployed Nov 13, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk:unknown Advisory evidence unavailable or changed; no merge permission risk-shadow:high Shadow-only risk signal: high

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant