Validate manifest schema bounds and common formats#4
Open
RitwijParmar wants to merge 1 commit into
Open
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.
Summary
ZeroPath's live MCP manifest already uses JSON Schema constraints such as
minLength,maxLength,minimum,maximum, andformatacross tool inputs. The current lightweight validator handles type/required/properties/composition, but it lets those constraints pass through unchecked.This PR extends the client-side validator to catch more malformed agent tool calls before they hit the ZeroPath API:
minLength/maxLengthminimum/maximumexclusiveMinimum/exclusiveMaximumpatternformatvalues used by API manifests:uuid,uri, andemailUnknown formats remain annotations instead of hard failures so adding a future format does not disable all client-side validation through
UnsupportedSchemaError.Why
For MCP users, these failures are easier to debug when the server rejects them locally with a structured validation issue instead of forwarding a bad UUID, out-of-range pagination value, or malformed URL/email to the API and surfacing a deeper backend error.
Tests
/Users/ritwij/Library/Python/3.9/bin/uv run --python 3.13 pytest -q/Users/ritwij/Library/Python/3.9/bin/uv run --python 3.13 python -m compileall src testsgit diff --check