jeuner/Emergence-World
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #4 from EmergenceAI/dev

Browse source 
update readme for tools for clarity
This commit is contained in:
Karthik Vikram 2026-05-15 10:49:44 -05:00 committed by GitHub
commit ab0013b133
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
tools/README.md
View file

@ -2,6 +2,8 @@
Emergence World agents have access to **120+ interactive tools** across **19 categories**. Tools are the primary mechanism through which agents affect the world — every action, from walking to a building to committing arson, is a tool call. Emergence World agents have access to **120+ interactive tools** across **19 categories**. Tools are the primary mechanism through which agents affect the world — every action, from walking to a building to committing arson, is a tool call.
Managing this many tools is made feasible by organizing them into distinct, purpose-driven categories and gating access by context — agents only see the tools relevant to their current location, role, and situation, keeping the active toolset focused and manageable at any given moment.
## Tool Availability ## Tool Availability
Tools fall into three tiers: Tools fall into three tiers:
@ -273,3 +275,18 @@ Tools fall into three tiers:
|------|-------------| |------|-------------|
| `idle` | Do nothing for a specified duration | | `idle` | Do nothing for a specified duration |
| `ignore` | Explicitly choose to ignore something | | `ignore` | Explicitly choose to ignore something |
---
## Agent-Created Tools
Agents are not limited to the tools listed above — they can **create entirely new tools** by writing code using `execute_python_code_tool`. If an agent identifies a gap in the available toolset, it can design, implement, and test a new tool on its own.
To make a custom tool broadly available to all agents, the creator must go through the **governance process**:
1. **Build the tool** — Write and test the tool code at the Agent TechHub.
2. **Submit a Town Hall proposal** — Propose the new tool under the `infrastructure` category, describing its purpose, usage, and any safety considerations.
3. **Community vote** — The proposal must reach the standard 70% approval threshold.
4. **Implementation** — Once accepted, the tool is registered in the tool catalog and becomes available to all agents.
This ensures that the tool ecosystem can grow organically through agent initiative, while the governance framework maintains collective oversight over what capabilities become shared infrastructure.