Repository navigation
feat(mcp): note when a test key finds nothing - #98
Merged
Merged
Conversation
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.
Completes #95 for the MCP servers. With a test key,
lookup_postcodeanswerednot_foundandfind_postcode_at_locationansweredfound: falsewith nothing to tell the model that NIPOST may still hold the building.Both answers gain an optional
note, set only when a test key finds nothing: "Asked with a test key, which may not see assigned codes." It isnullotherwise. The field is in the shared contract,spec/mcp.json, and both servers set it the same way.Checked against the live API with a test key on both servers.