Remove maxLength from MCP tool JSON schemas

[nathanjcochran]

Some models/providers don't support the maxLength JSON Schema config option for limit string length (such as Sonnet 4.5 when run through Vertex, as when using Google Antigravity). This can cause the MCP server to completely break the AI agent.

This fixes the problem by simply removing the maxLength config. We were using it to limit the length of service names (to match the back-end validation), but it's probably unlikely that users will hit the length limit often anyways, and if they do, they'll just get an error from the backend that explains the problem, and the LLM can retry:

> Create a new database service with a very long name (200 characters at least)

⏺ tiger - Create Database Service (MCP)(name: "this-is-a-very-long-database-service-name-that-exceeds-the-typical-length-limits-for-testing-purposes-and-to-see-how-the-system-handles-extrem
                                       ely-long-names-with-many-characters-in-them-which-should-be-at-least-two-hundred-characters-long-to-meet-the-requirement")
  ⎿  Error: service name cannot be longer than 128 characters

⏺ The system doesn't allow service names longer than 128 characters. The maximum length is 128 characters.

  Would you like me to create a service with a 128-character name instead (the maximum allowed)?