4 ms·
This is overly cynical. Models typically do know what tools they have access to because the tool descriptions are in the prompt. Asking a model which tools it h
by mgraczyk 2y ago
This is overly cynical. Models typically do know what tools they have access to because the tool descriptions are in the prompt. Asking a model which tools it has is a perfectly reasonable way of learning what is effectively the content of the prompt.
Of course the model may hallucinate, but in this case it takes a few clicks in the dev tools to verify that this is not the case.
- noosphr 2y ago>Of course the model may hallucinate, but in this case it takes a few clicks in the dev tools to verify that this is not the case. I don't know - or care to figure out - how OpenAI does their tool calling in this specific case. But moving tool calls to the end user is _monumentally_ stupid for the latency if nothing else. If you centralize your function calls to a single model next to a fat pipe it means that you halve the latency of each call. I've never build, or seen, a function calling agent that moves the api function calls to client side JS.
- mgraczyk 2y agoIt's not client side, the messages are in the api though. But what do you mean you don't care? The thing you were responding to was literally a claim that it was a tool call rather than direct output
- echelon 2y agoNone of this really matters. It could be either case. The thing we need to worry about is whether a Chinese company will drop an open source equivalent.
- PeterStuer 2y agoYou should check out Claude desktop or Roo-Code or any of the other MCP client capable hosts. The whole idea of MCP is providing a universal pluggable tool api to the generative model.