Activity

1. Kehrlann commented on Apr 2, 2026

   

   Kehrlann

   on Apr 2, 2026

   Contributor

   More actions

   Hey @tim-schneider-elo - good point. We're feeling some pains related to this in #697 .

   We'll investigate what we can do about this.

   Reacted by Tim Schneider
2. Kehrlann

   added

   enhancementNew feature or requestNew feature or request

   area/mcp-schema

   P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable feature

   waiting for triage

   on Apr 2, 2026
3. Kehrlann

   self-assigned this

   on Apr 2, 2026
4. tzolov commented on Apr 2, 2026

   

   tzolov

   on Apr 2, 2026

   Contributor

   More actions

   The right approach is to remove the JsonSchema in favor of Map<String, Object>. The reason is that the JSON Schema can not be mapped to a proper type without loosing json schema functionality.

   There are related PRs like this: #749
5. Kehrlann

   closed this as completedin 9520323on Apr 10, 2026
6. ashakirin

   added 2 commits that reference this issue on Apr 10, 2026

   fix: Remove JsonSchema and use a Map for inputSchema to support json …

   This issue will close once commit 9520323 is merged into the 'main' branch.

   9520323

   fix: Remove JsonSchema and use a Map for inputSchema to support json …

   This issue will close once commit e8bd7e8 is merged into the 'main' branch.

   e8bd7e8