CAMEL-24369: camel-mcp-server-starter: publish MCP tool annotations, fix json-schema-validator resolution

[Croway]

JIRA: 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

[davsclaus]

Clean, well-scoped PR that fixes two real bugs in the MCP server starter.

Highlights:

• applyAnnotations is a line-for-line match of the Vert.x engine in camel core — verified against VertxMcpServerEngine.java. The conformance gap between runtimes is eliminated: unset hints are omitted (not defaulted), title maps to the tool's top-level title
• Scope fix for camel-ai-tool is correct: camel-mcp-server-api already declares it at compile scope, so the starter's explicit <scope>test</scope> was winning by nearest-declaration and hiding AiToolAnnotations from the compile classpath
• json-schema-validator 3.0.0 pin is pragmatic — the MCP SDK's mcp-json-jackson3 needs the Jackson3-based 3.x line, while Camel manages 2.0.x for other components. The comment explains the problem clearly
• Tests are well-targeted: one verifying hints are published for an annotated tool, one verifying that a hint-less tool has null annotations — conformance assertions against the MCP client view

This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.