Skip to content

chore: update ChatGPT shipment test case - #340

Merged
dodeja merged 1 commit into
mainfrom
cursor/update-chatgpt-case-3-d749
Aug 21, 2026
Merged

chore: update ChatGPT shipment test case#340
dodeja merged 1 commit into
mainfrom
cursor/update-chatgpt-case-3-d749

Conversation

@dodeja

@dodeja dodeja commented Aug 21, 2026

Copy link
Copy Markdown
Member

Summary

  • update only ChatGPT app submission test case 3
  • request the 10 most recently updated shipments without nested containers
  • document the expected unfiltered list_shipments arguments and pagination behavior

Verification

  • jq empty chatgpt-app-submission.json
  • verified five positive and three negative test cases remain, with case 3 matching the requested schema fields and exact prompt
  • all PR checks passed
Open in Web Open in Cursor 

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Greptile Summary

This PR revises ChatGPT app-submission case 3 to request ten recent shipments without nested containers.

  • Replaces the active-tracking filter with an unfiltered shipment request.
  • Specifies a page size of ten, disabled container inclusion, and conditional pagination output.
  • Introduces an update-time ordering expectation that the shipment tool cannot satisfy.

Confidence Score: 4/5

The test case should be corrected before merging because it requests shipment ordering that the invoked tool cannot produce.

The changed prompt asks for the most recently updated shipments, but list_shipments exposes no update-time sort and the backend contract orders shipments by creation date.

Files Needing Attention: chatgpt-app-submission.json

Important Files Changed

Filename Overview
chatgpt-app-submission.json Updates submission case 3, but requests most-recently-updated ordering while the tool only returns creation-date-ordered shipments.

Fix all with Greploop Fix All in Codex Fix All in Claude Code

Prompt To Fix All With AI
### Issue 1
chatgpt-app-submission.json:151
**Unsupported update-time ordering**

When ChatGPT evaluates this case, `list_shipments` cannot fulfill “most recently updated” because the endpoint exposes no update-time sort and orders results by creation date. A conforming invocation therefore returns the most recently created shipments, causing this case to validate an inaccurate response or fail a correct implementation.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "chore: update ChatGPT shipment test case" | Re-trigger Greptile

Greptile also left 1 inline comment on this PR.

Co-authored-by: Akshay Dodeja <dodeja@gmail.com>
@vercel

vercel Bot commented Aug 21, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
api Ready Ready Preview Aug 21, 2026 7:53pm

Request Review

@dodeja
dodeja marked this pull request as ready for review August 21, 2026 19:56
@dodeja
dodeja merged commit 22259f4 into main Aug 21, 2026
23 checks passed
"description": "List actively tracked shipments without nested containers.",
"user_prompt": "Show the first 10 shipments where shipping-line tracking has not stopped. Do not include nested containers.",
"description": "List the 10 most recently updated shipments without nested containers.",
"user_prompt": "Show my 10 most recently updated shipments. Don’t include nested containers.",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Unsupported update-time ordering

When ChatGPT evaluates this case, list_shipments cannot fulfill “most recently updated” because the endpoint exposes no update-time sort and orders results by creation date. A conforming invocation therefore returns the most recently created shipments, causing this case to validate an inaccurate response or fail a correct implementation.

Prompt To Fix With AI
This is a comment left during a code review.
Path: chatgpt-app-submission.json
Line: 151

Comment:
**Unsupported update-time ordering**

When ChatGPT evaluates this case, `list_shipments` cannot fulfill “most recently updated” because the endpoint exposes no update-time sort and orders results by creation date. A conforming invocation therefore returns the most recently created shipments, causing this case to validate an inaccurate response or fail a correct implementation.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Fix in Codex Fix in Claude Code

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5326f208a8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"description": "List actively tracked shipments without nested containers.",
"user_prompt": "Show the first 10 shipments where shipping-line tracking has not stopped. Do not include nested containers.",
"description": "List the 10 most recently updated shipments without nested containers.",
"user_prompt": "Show my 10 most recently updated shipments. Don’t include nested containers.",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use an ordering supported by list_shipments

When an older shipment has been updated after newer shipments, this test cannot return the requested account-wide top 10: the list_shipments schema in packages/mcp/src/server.ts exposes no updated-time or sort argument, while the source-of-truth GET /shipments operation in docs/openapi.json orders results by creation date. Fetching a page of 10 and sorting it locally would still omit recently updated records outside that page, making the submission case unsatisfiable or encouraging an inaccurate response; use the API's creation-date ordering or restore a supported filter-based case.

AGENTS.md reference: AGENTS.md:L27-L27

Useful? React with 👍 / 👎.

@vorflux vorflux Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary

Reviewed — found 1 issue. This PR updates the ChatGPT submission test for list_shipments; I reviewed the changed prompt and expected output against the tool’s supported ordering behavior.

Findings

chatgpt-app-submission.json

  1. The test requires update-time ordering that list_shipments does not support.

Verdict

⚠️ Changes requested. The revised test expects “most recently updated” shipments even though the tool can only rely on the endpoint’s creation-date ordering.


Review with Vorflux

"description": "List actively tracked shipments without nested containers.",
"user_prompt": "Show the first 10 shipments where shipping-line tracking has not stopped. Do not include nested containers.",
"description": "List the 10 most recently updated shipments without nested containers.",
"user_prompt": "Show my 10 most recently updated shipments. Don’t include nested containers.",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

list_shipments cannot order by update time; /shipments is ordered by creation date and exposes no sort parameter. Please change this prompt and expected output to "most recently created shipments," or add supported update-time ordering before using this test case.

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.

2 participants