Tools are what turn a chatbot into an agent that can act: search, look up, calculate, send.
What a tool is
A tool is a node or workflow the agent may call, such as reading a sheet, calling an API, searching documents or running a sub-workflow (sub-workflows).
Describe tools clearly
The agent chooses tools using their names and descriptions. Say what the tool does, what input it needs and when to use it. Vague descriptions cause wrong choices.
Limit power
- Prefer read-only tools first.
- For tools that send or change data, require approval (human approval).
- Restrict inputs, for example allowed sheets or fields.
Keep the toolset small
Too many tools confuse the agent. Give it only what the job needs.
Test failures
Check what happens when a tool errors or returns nothing. The agent should say so, not invent an answer.
MCP
n8n also supports MCP-related nodes for connecting agents to tools through the Model Context Protocol. It is an advanced topic; learn the basics first.
Quick answers
What can an agent tool be?
A node, an API call or a sub-workflow.
Why does the agent choose the wrong tool?
Tool descriptions may be vague or too many tools exist.
Should tools be able to send messages?
Only with approval for risky actions.
Related reading
- What Is an AI Agent in n8n and How Is It Different from a Workflow?
- How to Build Your First AI Agent in n8n, Step by Step
- n8n AI Agent Memory Explained: How an Agent Remembers a Conversation
Ready to turn n8n into a real skill?
Join a practical, trainer-led n8n course with projects like lead capture, notification flows, an AI step and a tool-using agent. Ask for a free counselling call to see if it fits your goal.
See the 15-day n8n training | Find your city | Book free counselling