davsclaus opened a new pull request, #26483:
URL: https://github.com/apache/camel/pull/26483

   `camel mcp` exposed 83 tools. Since CAMEL-24695 the shared authoring tools 
answer the questions 14 older per-kind tools were written for, so a client had 
two near-identical tools for the same question: more schema to read, and the 
choice between them is where small models pick the weaker one (CAMEL-24698). No 
client uses the older names, so this is a straight removal in 4.23, with the 
two gaps the shared tools still had closed first.
   
   **Shared tools before the removal**
   
   - `CamelCatalog.suggestEipNames(term, max)` next to the component, data 
format and language ones: the `CatalogTermMatcher` already ranked the EIP 
aliases of CAMEL-23833 (`fan-out`, `dedup`, `rate-limit`), it was only not 
wired to the EIPs.
   - `camel_catalog_find` takes `kind=eip` (and searches the EIPs when no kind 
is given); `camel_catalog_doc` falls back to the best alias or title match when 
the name is not an EIP (`rate-limit` returns the throttle doc with 
`matchedTerm`), and the not-found suggestions include the EIPs.
   - `camel_catalog_doc` takes `includeHeaders` (the `CamelXxx` header names, 
constants, types and group that `camel_catalog_component_doc` returned since 
CAMEL-23793) and returns the `version` next to `groupId`/`artifactId`.
   
   **Removed** (`CatalogTools` keeps `camel_catalog_docs`, `TransformTools` 
keeps `camel_transform_route`, `RuntimeTools` keeps the other 28)
   
   | Removed | Use instead |
   |---|---|
   | `camel_catalog_component_doc`, `camel_catalog_dataformat_doc`, 
`camel_catalog_language_doc`, `camel_catalog_eip_doc` | `camel_catalog_doc` 
with the kind |
   | `camel_catalog_component_maven` | `camel_catalog_doc` (Maven coordinates) |
   | `camel_catalog_components`, `camel_catalog_dataformats`, 
`camel_catalog_languages`, `camel_catalog_eips` | `camel_catalog_find` with the 
kind |
   | `camel_validate_yaml_dsl`, `camel_validate_route` | 
`camel_validate_source`; a URI alone by `camel_catalog_doc endpoint=` |
   | `camel_runtime_eval` / `camel_runtime_errors` / `camel_runtime_stop` | 
`camel_eval_expression` / `camel_get_errors` / `camel_control action=stop` |
   
   The `camel_build_integration` prompt names the shared tools now. The 
`runtime` (`spring-boot`, `quarkus`) and `platformBom` catalog arguments of the 
removed tools have no equivalent on the shared tools (decided on the JIRA: the 
core catalog is what the MCP is used for; `CatalogService` stays for the kept 
tools that take them).
   
   **Tests**: `CamelCatalogTest` (aliases), `CatalogDocsTest` (find by alias, 
doc fallback, headers, version), `CatalogToolsTest` became `CatalogServiceTest` 
for the repos, BOM and version checks it exercised through the removed tools, 
plus a `camel_catalog_docs` test; the serialization, prompt, transform and 
runtime tests dropped the removed tools. `camel-catalog`, `camel-jbang-core` 
and `camel-jbang-mcp` test suites pass, and the TUI `AiPanelPromptBudgetTest` 
stays within its core budget (4291/4300 tokens) after the `includeHeaders` 
parameter.
   
   **Docs**: the MCP page lists the shared tools and `camel_catalog_docs` 
instead of the removed ones; the 4.23 upgrade guide carries the old → new 
mapping.
   
   _Claude Code on behalf of davsclaus_
   
   🤖 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