Croway opened a new pull request, #27512: URL: https://github.com/apache/camel/pull/27512
Found while running LLM evals of agents that use the Camel MCP server shipped with 4.22.1. An agent calling `camel_catalog_language_doc` with no platform BOM had to send one, because the schema made `runtime`, `camelVersion` and `platformBom` required: it sent `"platformBom": ""`, which failed with `platformBom must be in GAV format (groupId:artifactId:version), got:`, and omitting it fails with `Missing required argument: platformBom`. The catalog doc tools were effectively unusable without inventing a BOM. On main this is fixed as part of the shared authoring tools (CAMEL-24695, CAMEL-24698), which cannot be backported as such; this is a targeted fix for 4.22.x: - **Optional arguments** (144): `runtime`, `camelVersion`, `platformBom`, `filter`, `label`, `limit`, `level` and `nameOrPid` where the tool handles them being absent (catalog resolution, null-safe filter helpers, single-process auto-detection), and the arguments documented as optional or with a default. - **Catalog resolution from main**: a blank `platformBom` or `camelVersion` means none; a `camelVersion` that is not a version (`main`, `latest`) or the version in use is the default catalog; a version that cannot be downloaded falls back to the default catalog for the main runtime. - **`platformBom` with the main runtime**: a value that is not an `org.apache.camel` GAV is ignored instead of failing (same as the companion change on main). - **`camel_runtime_memory_leak`**: an omitted `mode` records in dual mode, as documented. `CatalogToolsTest` is updated for the BOM behaviour and covers the empty-`platformBom` call; the `camel-jbang-mcp` tests pass (415). -- 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]
