DOC: Multi-agent Systems #301

Closed
opened 2026-02-20 17:36:00 -05:00 by yindo · 1 comment
Owner

Originally created by @kellerkind84 on GitHub (Nov 5, 2024).

Issue with current documentation:

I think there is an issue with the "Supervisor (as tools)" graphic. It implies that the LLM picks from a number of tools. I don't think that is correct, since only agents pick from tools and everything that is not picked by an agent is a node and therefore requires an edge per node to be called. This is also correctly implemented in the example.

Idea or request for content:

Simply replace the "llm" with "agent".
You might as well add some tool-definition to the "Supervisor with tools" example for the tools, since it makes it sound like there is no tool definition necessary (which could also lead to no clear distinction between a node and a tool).

Originally created by @kellerkind84 on GitHub (Nov 5, 2024). ### Issue with current documentation: I think there is an issue with the "Supervisor (as tools)" graphic. It implies that the LLM picks from a number of tools. I don't think that is correct, since only agents pick from tools and everything that is not picked by an agent is a node and therefore requires an edge per node to be called. This is also correctly implemented in the example. ### Idea or request for content: Simply replace the "llm" with "agent". You might as well add some tool-definition to the "Supervisor with tools" example for the tools, since it makes it sound like there is no tool definition necessary (which could also lead to no clear distinction between a node and a tool).
yindo closed this issue 2026-02-20 17:36:00 -05:00
Author
Owner

@vbarda commented on GitHub (Nov 5, 2024):

@kellerkind84 which page are you referencing?

I think there is an issue with the "Supervisor (as tools)" graphic. It implies that the LLM picks from a number of tools. I don't think that is correct, since only agents pick from tools and everything that is not picked by an agent is a node and therefore requires an edge per node to be called. This is also correctly implemented in the example.

but the LLM does pick from a number of tools in this case -- the agent (supervisor) is simply a tool-calling LLM and the individual agents it's delegating to are wrapped as tools. i am not sure i understand your concern

You might as well add some tool-definition to the "Supervisor with tools" example for the tools, since it makes it sound like there is no tool definition necessary (which could also lead to no clear distinction between a node and a tool).

in the supervisor with tools example we use a prebuilt ReAct agent with functions as tools (e.g. agent_1 and agent_2 are tools in this case)

@vbarda commented on GitHub (Nov 5, 2024): @kellerkind84 which page are you referencing? > I think there is an issue with the "Supervisor (as tools)" graphic. It implies that the LLM picks from a number of tools. I don't think that is correct, since only agents pick from tools and everything that is not picked by an agent is a node and therefore requires an edge per node to be called. This is also correctly implemented in the example. but the LLM _does_ pick from a number of tools in this case -- the agent (supervisor) is simply a tool-calling LLM and the individual agents it's delegating to are wrapped as tools. i am not sure i understand your concern > You might as well add some tool-definition to the "Supervisor with tools" example for the tools, since it makes it sound like there is no tool definition necessary (which could also lead to no clear distinction between a node and a tool). in the [supervisor with tools example](https://langchain-ai.github.io/langgraph/concepts/multi_agent/#supervisor-tool-calling) we use a prebuilt ReAct agent with functions as tools (e.g. `agent_1` and `agent_2` are tools in this case)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraph#301