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

   Stacked on #26604 (base is its branch, so only this change shows in the 
diff; GitHub retargets to main when #26604 merges).
   
   The MCP tools `camel_catalog_examples` / `camel_catalog_example_file` in 
camel-jbang-mcp, and `list_examples` / `get_example_file` in the 
camel-jbang-core AI tool registry, lagged behind the reorganized examples 
catalog (CAMEL-24824):
   
   - in camel-jbang-mcp the three arguments were not declared optional, so a 
call without all of them failed with `Missing required argument: filter` (then 
`level`, then `limit`)
   - the descriptions still spoke of a difficulty level (beginner, 
intermediate, advanced) while the catalog now has the 11 group levels, so an 
agent filtered with values that match nothing
   - the new metadata (order, teaches, infraServices) was not returned and 
there was no way to get the groups with their title and intro
   - the core registry capped the result at 20 with no limit argument, so an 
unfiltered listing dropped half of the 40 examples
   
   Now both tools:
   
   - take optional `filter`, `level` (a group) and `limit` (default 50)
   - return `groups` (level, title, intro, count) and the `examples` in reading 
order, each with `order`, `teaches` (components, eips, languages, dataformats), 
`infraServices`, `bundled` and `files`, plus `count` and `total`
   - describe the groups instead of difficulty levels
   
   `ExampleHelper.getTeaches` is the new map accessor; `getTeachesSummary` now 
builds on it. Tests: `ExampleToolsTest` (new, 3) and two cases in 
`ToolRegistryTest`.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj


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