JiriOndrusek opened a new issue, #9299: URL: https://github.com/apache/camel-quarkus/issues/9299
### Describe the feature here Camel 4.23 adds structured tool output to `ai-tool` (CAMEL-24333): `outputSchema` / `outputParameter.*`. `QuarkusMcpServerEngine` does not wire it yet, including on the `camel-main` branch: - `tools/list` has no `outputSchema`: `McpServerTool.outputSchemaJson()` is ignored. - `tools/call` returns only `TextContent`: `McpToolCallResult.structuredContent()` is dropped. Camel's own engine does both: `VertxMcpServerEngine#toolAdded` and `#buildMcpTool`. ### Impact (Quarkus + Camel 4.23) - `outputSchema` has no effect over MCP; clients get text only. - Nothing warns about it. The bridge has a warning only for engines without resource support (`supportsResources()`), not for structured output. Nothing is broken on `main` today: Camel 4.22 has no structured output. The caller-identity part of engine parity is tracked in CAMEL-25406. Related: #8950, #8967 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
