Croway opened a new pull request, #1881:
URL: https://github.com/apache/camel-spring-boot/pull/1881

   JIRA: [CAMEL-24369](https://issues.apache.org/jira/browse/CAMEL-24369) — 
companion PRs: apache/camel#25404 and one in apache/camel-quarkus.
   
   Two fixes found by running the same ai-tool + mcp-server application on 
Camel Main, Spring Boot and Quarkus:
   
   1. **MCP tool annotation hints were dropped.** 
`SpringAiMcpServerEngine.toolAdded()` published only 
name/description/inputSchema; `title`, `readOnlyHint`, `destructiveHint`, 
`idempotentHint`, `openWorldHint` — which the Vert.x engine publishes and the 
ai-tool/mcp-server docs promise are passed to the engine — were silently lost. 
The engine now maps them exactly like the Vert.x engine (unset hints are not 
published). This required promoting the starter's `camel-ai-tool` dependency 
from test to compile scope: the direct test-scope declaration overrode the 
transitive compile scope from `camel-mcp-server-api`.
   
   2. **Startup failure with the documented BOM setup** 
(`camel-spring-boot-bom` + `spring-boot-dependencies`): the Spring AI MCP 
server validates tool arguments through `mcp-json-jackson3`, which requires the 
Jackson3-based `com.networknt:json-schema-validator:3.0.x`; nearest-wins 
resolution picked a 2.0.x (Jackson2 API) instead, failing with 
`NoSuchMethodError: Schema.validate(tools.jackson.databind.JsonNode)`. The 
starter now declares 3.0.0 directly so applications resolve it out of the box.
   
   Two new conformance tests cover the annotations (published hints + no 
annotations for hint-less tools); the full starter suite passes (13 tests).
   
   ---
   _Claude Code on behalf of Croway (Federico Mariani)_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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]

Reply via email to