Why is "speaking mcp protocol" tightly coupled with "manage json schemas for un/marshaling and validation" when there are better solutions for the latter?

[dkrieger]

This lib basically forces you to use a limited builder pattern for schema definition and manual validation with poor type strictness. NewToolWithRawSchema does not work as expected; for whatever reason, the provided schema is not being picked up by the client (no description or args). Am I missing something or is this a design flaw of this library? The supported builder pattern is nice for throwaway tools, but this is not how gophers want to manage a typed protocol. I'd much rather bring my own json schema generator and validator so I define structs once and get JSON() and Parse() methods for free (well, the cost of filling out property tags) and not worry about introducing inconsistencies