Often, an agent is called upon after a user enters a prompt into a chat interface. In the Nextworld platform this could be in Ed, or Ed the Builder inside Project Builder. Once the agent receives the prompt, it looks at its hierarchy of child agents and skills to determine whether it is capable of fulfilling the request, or if it needs to delegate it to one of its child agents.
Compare this experience to a carpentry project. You, the user, have a project that you want completed. You can provide a detailed plan or a high level description of what you want to Ed, the foreman. Ed determines what parts of the project he himself can do, and then looks at his network of specialized contractors and delegates the tasks that are best suited to each of their skills.
The table below reviews the different metadata types used in our agent framework, and compares each component to a part of this hypothetical carpentry project:
| Component | Description | Non-Technical Comparison |
|---|---|---|
| Agents | Agents perform tasks across your platform on behalf of users and automated processes. | The top most agent in the hierarchy, Ed, is the foreman on the job site. He is who you talk to when you need something built. He takes the request, figures out the requirements, then coordinates the right agents and resources to get it done. Agents in Ed's hierarchy are the skilled contractors. Each agent has their own expertise, skills, and tools. |
| Skills | A skill defines how an agent thinks and behaves when handling a request. It is comprised of instructions written in natural language that are embedded in an agent's system prompt at runtime. An agent can have many skills, or none at all, depending on the complexity of the tasks it handles. | A skill is a blueprint. It gives the contractor plain-language instructions on how to complete a task. |
| Tools | A tool is an individual action that an agent can execute. A tool could be as simple as retrieving data, or as complex as a multi-sequence operation that requires other agents and tools. Tools can be:
| Agent tools are the tools in a contractor's toolbox that they can use to perform tasks. Once a contractor receives a project, they determine which tools they need to use. MCP tools are the tools that come with the job site. They are available for any contractor to use. |
| Tool set | A group of agent tools. A tool set can be used by one, or many agents, once it has been defined and added to their configuration. | A toolbox that contains all of the contractor's personal tools for completing their tasks. A contractor (agent) could have many different tool sets that they use for different tasks. |
| MCP Server | The MCP server is the infrastructure that gives agents the ability to take action in the platform, such as updating records, triggering workflows, and interacting with application data. Without it, agents can reason and retrieve but cannot make changes. The platform builds and maintains the server and determines what tools and resources it provides. | The building's systems, such as electrical plumbing, and infrastructure. Without being connected to these systems, a contractor can plan and measure, but cannot make real changes to the structure. |
| MCP Bundle | An MCP Bundle is how you define which metadata, such as tables and logic blocks, are exposed through the MCP server. Partners and customers build and maintain their own bundles, packaging the specific resources they want available to MCP clients. | A bundle specifies which rooms the contractor has access to. |
Improve agent tool selection
The SearchTools tool helps agents with large tool sets select the most relevant tools for a given task, reducing context and improving selection accuracy.
When an agent has more than 10 tools configured, the platform automatically enables SearchTools, a system tool that helps the agent find the most relevant tools for a given task. Rather than exposing all available tools at once, SearchTools allows the agent to search for and retrieve the ten most relevant tools based on the context of the conversation.
SearchTools is enabled automatically and requires no configuration. However, the quality of your agent's tool descriptions directly affects how accurately SearchTools can identify the right tools. Well-written tool descriptions help the agent retrieve the most relevant tools and reduce the chance of selecting an incorrect one.
Tips for writing effective tool descriptions
- Be specific about what the tool does and when to use it.
- Include relevant keywords a user might use when asking for that capability.
- Avoid vague or overlapping descriptions across tools. If two tools sound similar, the agent may select the wrong one.
- Use Enrich from Capabilities in the Agent Builder record to automatically improve your agent's description based on its configured tools and child agents. Learn more in Agent Builder application.