tools.json Schema Validation Guide
Standardize tool metadata so crawlers and AI agents can parse capabilities consistently.
1. Validate required fields: name, url, input, output, and category.
2. Keep type definitions stable across all tool entries.
3. Ensure endpoint URLs are absolute, secure, and reachable.
4. Reject unknown properties to prevent silent parser drift.
5. Version schema changes and provide migration notes.
6. Re-run schema checks in CI before publishing.
Implementation notes
Keep one schema owner and changelog. Most ingestion regressions are caused by undocumented field changes, so version bumps and migration notes are critical for reliable downstream parsing.
Related pages
FAQ
Is JSON Schema enough? It covers structure; operational checks still need endpoint health and semantic validation.
How often should schema checks run? At minimum on each PR and release candidate build.