SimpleChatTC: ToolCall hs info in normal assistant-user chat flow
Also as part of same, wrap the request details in the assistant block using a similar tagging format as the tool_response in user block.
This commit is contained in:
parent
30aa2f4c6b
commit
fd662b4b0b
|
|
@ -300,6 +300,8 @@ work.
|
||||||
|
|
||||||
### Tool Calling
|
### Tool Calling
|
||||||
|
|
||||||
|
#### Extending wiht new tools
|
||||||
|
|
||||||
Provide a descriptive meta data explaining the tool / function being provided for tool calling.
|
Provide a descriptive meta data explaining the tool / function being provided for tool calling.
|
||||||
|
|
||||||
Provide a handler which should implement the specified tool / function call. It should place
|
Provide a handler which should implement the specified tool / function call. It should place
|
||||||
|
|
@ -311,6 +313,23 @@ Update the tc_switch to include a object entry for the tool, which inturn icnlud
|
||||||
* a reference to the handler and also
|
* a reference to the handler and also
|
||||||
* the result key
|
* the result key
|
||||||
|
|
||||||
|
#### Mapping tool calls and responses to normal assistant - user chat flow
|
||||||
|
|
||||||
|
Instead of maintaining tool_call request and resultant response in logically seperate parallel
|
||||||
|
channel used for requesting tool_calls by the assistant and the resulstant tool role response,
|
||||||
|
the SimpleChatTC pushes it into the normal assistant - user chat flow itself, by including the
|
||||||
|
tool call and response as a pair of tagged request with details in the assistant block and inturn
|
||||||
|
tagged response in the subsequent user block.
|
||||||
|
|
||||||
|
This allows the GenAi/LLM to be aware of the tool calls it made as well as the responses it got,
|
||||||
|
so that it can incorporate the results of the same in the subsequent chat / interactions.
|
||||||
|
|
||||||
|
NOTE: This flow tested to be ok enough with Gemma-3N-E4B-it-Q8_0 LLM ai model for now.
|
||||||
|
|
||||||
|
TODO: Need to think later, whether to continue this simple flow, or atleast use tool role wrt
|
||||||
|
the tool call responses or even go further and have the logically seperate tool_call request
|
||||||
|
structures also.
|
||||||
|
|
||||||
|
|
||||||
### Debuging the handshake
|
### Debuging the handshake
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -74,7 +74,7 @@ class AssistantResponse {
|
||||||
if (this.response.content !== "") {
|
if (this.response.content !== "") {
|
||||||
return this.response.content;
|
return this.response.content;
|
||||||
} else if (this.response.toolname !== "") {
|
} else if (this.response.toolname !== "") {
|
||||||
return `ToolCall:${this.response.toolname}:${this.response.toolargs}`;
|
return `<tool_call>\n<tool_name>${this.response.toolname}</tool_name>\n<tool_args>${this.response.toolargs}</tool_args>\n</tool_call>`;
|
||||||
} else {
|
} else {
|
||||||
return ""
|
return ""
|
||||||
}
|
}
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue