N tools : 1 resource sever mapping and 1 resource server: 1 agent mapping
Open
Nobody has claimed this yet.
community-request
documentation
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 349
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 318
Description
The concept tutorials are great! They are very easy to follow and provides essential background.
One thing I feel will come up in cusotmer discussion about the mapping. I recommend that we make it clear that:
- Resource server is not a single tool server. It is a server for 1 or more tools. For example, in simple weather server, we only have 1 tool
get_weather. But in the Google search server, we have 2 toolsbrowseandsearch. - In the agent:server mapping YAML, we only allow 1 resource server mapped to a single agent.
- While you can have multiple agents running with a single
ng_runcommand, there is no orchestration between the multiple agents (e.g. the user need to work out a way to delegate the tasks to the different agents).
Please correct me if my understanding above is incorrect.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the concept tutorials and the agent:server mapping YAML, then inspect how ng_run handles multiple agents. Update the documentation to clarify resource-server tool counts, the one-server-per-agent mapping, and the lack of orchestration between agents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100