Retire the identity-field workaround - #60
Merged
Merged
Conversation
#59 told readers to put id and name in every `fields` array because the gateway blocked any array without them. amnotyoung/io-mcp#61 shipped, so the gateway fills both in and nothing blocks. Instructions written against a defect outlive it badly: they read as requirements, and the next person spends time satisfying one that no longer exists. Restores the three Skill files to their pre-#59 wording — the blocked-response sections lose the fields step they gained, and the callers that named id and name alongside description drop them again. Keeps one line, because one thing #59 found is still true and was never written down: every item carries id and name, so they come back whether or not the caller lists them. That is why the response echo can be longer than the request, which is otherwise a surprise with no explanation anywhere. The empty-projection fix (amnotyoung/io-mcp#62) needed no Skill change: it removed a false claim from responses rather than adding a rule for callers to follow. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
#59 told readers to put
idandnamein everyfieldsarray, because the gateway blocked any array without them. amnotyoung/io-mcp#61 has shipped and is verified against production — the gateway fills both in, and nothing blocks.Instructions written against a defect outlive it badly. They read as requirements rather than as workarounds, and the next person spends effort satisfying one that no longer exists.
Change
The three Skill files return to their pre-#59 wording:
fieldsstep they gainedkorean-oda-portfolio-lookupstep 4 and the comparison workflow, andinternational-oda-data-lookuproute 2, stop namingidandnamebesidedescriptionNet diff against the pre-#59 baseline is a single added bullet:
That one is kept because it is still true and was never documented: the echoed
fieldscan be longer than the request, which is otherwise a surprise with no explanation anywhere in the Skill.amnotyoung/io-mcp#62 (empty projections) needs no Skill change — it removed a false claim from responses rather than adding a rule for callers to follow.
Version 0.2.28 → 0.2.29;
npm test27/27.🤖 Generated with Claude Code