Reflect the latest changes on the schema

[rdimitrov]

Motivation and Context

Addressing #634 (comment)

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[rdimitrov]

Longer term I'd like to decide on a way to automate this. I have a branch in progress where upon promotion to prod -> we file a PR with the schema upon static and I'll file it once ready to bootstrap a discussions