Background image representing tools and capabilities that empower Playnex agents to act in the world.

Tools

How agents gain abilities — to browse, write, analyze, automate, and act.

Tools are what transform an agent from a thinker into a doer. They extend the agent’s abilities beyond language — giving it access to the web, files, scripts, APIs, and more. Tools are how agents touch the world.

Explore Tools →

1. What Are Tools?

Tools are capabilities you attach to agents. Each tool gives the agent a new ability — something it can do in the real world.

Examples include:

  • Web Browser — search, scrape, gather information
  • File Writer — create and edit files
  • Document Analyzer — summarize or extract insights
  • Script Runner — execute local scripts
  • API Caller — interact with external services

Tools turn agents into collaborators that can take action, not just generate text.


2. Adding a Tool to an Agent

To add a tool to an existing agent:

playnex agent add-tool my-agent

You’ll be prompted to choose from the available tools in the Playnex tool library.


3. Viewing an Agent’s Tools

To see which tools an agent has:

playnex agent view my-agent

This displays the agent’s purpose, model, tools, and memory configuration.


4. Removing a Tool

To remove a tool:

playnex agent remove-tool my-agent

Agents immediately lose access to that capability.


5. How Agents Use Tools

Tools are invoked automatically when the agent decides it needs them. For example:

  • If the agent needs information → it uses the browser tool
  • If it needs to save a draft → it uses the file writer
  • If it needs to analyze a PDF → it uses the document analyzer

You can also instruct the agent explicitly:

“Search the web for recent research on local-first AI.”

Tools give agents agency — the ability to act on your behalf.

With tools, agents become more than models. They become workers — capable, autonomous, and deeply useful.

Next Steps

Now that you understand tools, explore how agents coordinate together.

Learn About Orchestration →

Or return to the documentation overview.

Back to Docs →