Open michael-desmond opened 5 days ago
OpenMeteo
is a well-known service. Renaming is a challenging task because, in the future, you can have multiple weather forecast providers in the framework. How would you differentiate between them?What do you think @matoushavlena ?
@Tomas2D this is a broader issue around LLM capabilities and needing language that an LLM can traverse. LLMs shouldn't be expected to generate a plan to call OpenMeteo, they should be expected to plan to get_weather_forecast. @dakshiagrawal has proposed a layer of abstractions over common tools like search_internet that sits between branded tools and the LLM. This will (a) fix the problem descreibed by @michael-desmond and (b) enable greater flexibliity to add tools (e.g. if a developer pays for a subscription weather service). Off the bat I can think of this being very useful for users to bring their own RAG solutions to a Bee agent.
Is your feature request related to a problem? Please describe. Using openMeteo with Granite 3.0 8b and I ran into a few issues that may be worth us looking into. Also touches on the general topic of tool optimization.
openMeteo
is not language intuitive i.e. its not obviously descriptive of its function. As such the LLM will sometimes use the tool to perform actions its not intended for.Describe the solution you'd like