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

   ## Summary
   
   Slims down the four catalog list tools ([CAMEL-23473][jira]). Each list 
response previously
   included a multi-sentence `description` per item and could return up to 50 
items. The LLM rarely
   needs the description in a list — `name` + `title` are enough to decide what 
to drill into, and
   the matching `*_doc` tool already carries the description.
   
   ## Changes
   
   * `ComponentInfo`, `DataFormatInfo`, `LanguageInfo`, `EipInfo` records: 
removed the `description`
     field. Mapping methods updated accordingly.
   * `camel_catalog_components` and `camel_catalog_dataformats` default `limit` 
lowered from 50 to 20.
     `camel_catalog_languages` and `camel_catalog_eips` did not previously 
expose a `limit` argument
     and are left as-is.
   * `camel_catalog_components` tool description updated to reflect the new 
payload shape and to
     point at `camel_catalog_component_doc` for descriptions.
   * Upgrade-guide entry added under `camel-jbang-mcp` in 
`camel-4x-upgrade-guide-4_21.adoc`.
   
   ## Test plan
   
   - [x] `mvn -DskipTests install` in `dsl/camel-jbang/camel-jbang-mcp` 
(formats + builds)
   - [x] `mvn test` in `dsl/camel-jbang/camel-jbang-mcp` — 255 tests pass, 
including 2 new ones:
       * `listInfoRecordsCarryNoDescription` (reflective check across all four 
list records)
       * `defaultLimitCapsResultsAtTwenty` (asserts default `limit` returns ≤ 
20 items)
   - [x] `componentInfoNullFieldsAreOmittedFromJson` updated for the new 
`ComponentInfo` arity
   - [x] `mvn clean install -DskipTests` from repo root — full reactor build 
green, no uncommitted
         regenerated artifacts
   
   [jira]: https://issues.apache.org/jira/browse/CAMEL-23473
   
   ---
   _Claude Code on behalf of Andrea Cosentino_


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