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

   `camel_catalog_doc` for the `simple` language answers without a filter with 
the function count and the names by group, and tells the model that 
`optionsFilter` with "a function name, a group above or a word from its 
description" returns the matching functions with parameters and examples. But 
the filter was one substring match over name, display name, description and 
group, so a model that followed the hint got more than it asked for: `date` 
returned the two functions of the date group plus two more whose description 
mentions a date, and `string` returned 41 of the 152 functions since most 
descriptions say "string" somewhere. For a small local model that is a page of 
functions instead of a few with examples.
   
   ### What changes
   
   - A filter equal to a function group name (`date`, `string`, `core`, 
`collection`, ...) returns that group only; the answer carries `functionGroup`.
   - A filter equal to a function name, with or without its parameters 
(`random` or `random(min,max)`), puts that function first, then the word 
matches as before.
   - Operators the same way: a kind (`binary`, `logical`, `unary`, `ternary`, 
`chain`) returns that kind only with `operatorKind`, and an operator itself 
(`==`) comes first.
   - Any other word still matches names and descriptions, so nothing a model 
used to find is lost.
   
   The tool descriptions are unchanged (the local-model schema budget stays 
flat); the MCP page gained one sentence on how the filter resolves.
   
   ### Testing
   
   `CatalogDocsTest`: a new test for the group (`date` is exactly two, `string` 
is the group and not the catalog), the exact name in three spellings, the 
operator kind and the exact operator; the existing filter test keeps its 
expectations.
   
   _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