Claus Ibsen created CAMEL-24760:
-----------------------------------

             Summary: camel-jbang - the core tool set for local models: 
camel_catalog_find in it, prefix budgets raised, prompt lines for the canonical 
YAML shape and file writes
                 Key: CAMEL-24760
                 URL: https://issues.apache.org/jira/browse/CAMEL-24760
             Project: Camel
          Issue Type: Improvement
          Components: camel-jbang
            Reporter: Claus Ibsen


For a local model the assistant offers the core tool subset automatically (auto 
mode picks it for any local endpoint). Three things the benchmark traces 
(CAMEL-24698) and the preparation of the next series show:

* camel_catalog_find is not in the core set, for lack of room in the core 
prefix budget (4,291 of 4,300 estimated tokens after CAMEL-24712). It is the 
tool that turns a product or protocol name (postgres, mqtt, artemis) into a 
component, the first question of every intermediate example. Raise the core 
budget (it was measured for 19 tools and is a guard against accidental growth, 
not a model limit; a 32k context leaves ample room) and mark camel_catalog_find 
core.
* The kind descriptions of camel_catalog_doc and camel_catalog_find were 
trimmed to fit the full budget ("a bean is a built-in class such as 
StringAggregationStrategy", "bean with an interface name lists the built-in 
implementations"); with the budgets raised they come back, the text helps 
people too.
* Two lines missing from the system prompt that the traces earned: the 
canonical YAML shape (since CAMEL-24722 the shorthand a model writes from 
memory warns on every first run), and "write files with camel_write_file, never 
paste file contents in the answer" (the most frequent failure of a small model 
after a correct hint was answering with pasted files).

Small change, to be in the build the next benchmark series measures.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to