> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentscope.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For AgentScope Python, use https://docs.agentscope.io/stable/en/index for new projects. For existing projects, check the installed agentscope version and use matching versioned documentation.
> The /latest/ alias points to the newest documentation and may move ahead of /stable/ when a development version exists. Do not mix AgentScope 1.x and 2.x APIs.
> State the AgentScope version when providing installation commands or code examples. ReMe uses its own continuously updated /reme/latest/ documentation.

# Overview

> Equip agents with tools, MCP servers, and skills through the toolkit

Tools are how an agent acts on the world: running shell commands, reading files, calling APIs. Each tool exposes itself to the LLM as a JSON Schema, and the agent invokes it through a unified streaming interface.

AgentScope organizes tool-related building blocks under three concepts:

| Concept | Role |
| - | - |
| **Tool** | Any class that satisfies the `ToolBase` interface, including the built-ins shipped with AgentScope and the `FunctionTool` / `MCPTool` adapters that wrap plain functions or MCP-server tools |
| **Toolkit** | The container that registers tools, MCP clients, and skills, exposes their JSON schemas to the model, and dispatches each tool call to the right tool object |
| **Tool Group** | A named bundle of tools, MCP clients, and skills that can be activated or deactivated as a unit; the agent toggles groups at runtime via the built-in meta tool |

A minimal `Toolkit` takes a list of tool instances:

```python theme={null}
from agentscope.tool import Toolkit, Bash, Read, Write, Edit

toolkit = Toolkit(
    tools=[Bash(), Read(), Write(), Edit()],
)
```

A `Toolkit` created with `tools` alone exposes those tools in the special `"basic"` group, which is always active. Adding `mcps`, `skills_or_loaders`, or extra `tool_groups` extends what the agent can reach.

## Next Steps

Each capability source has its own page:

> **[Python Tool](https://docs.agentscope.io/en/versions/2.0.12dev/building-blocks/tool/python-tool.md)**
>
> Built-in tools, custom tools, function wrapping, and tool middleware.

> **[MCP](https://docs.agentscope.io/en/versions/2.0.12dev/building-blocks/tool/mcp.md)**
>
> Connect MCP servers and use their tools.

> **[Skill](https://docs.agentscope.io/en/versions/2.0.12dev/building-blocks/tool/skill.md)**
>
> Extend agent capabilities with markdown instruction sets.

> **[Meta Tool](https://docs.agentscope.io/en/versions/2.0.12dev/building-blocks/tool/manage-tools.md)**
>
> Let the agent activate and deactivate tool groups at runtime.

## Further Reading

> **[Agent](https://docs.agentscope.io/en/versions/2.0.12dev/building-blocks/agent/overview.md)**
>
> How agents orchestrate tool calls in the ReAct loop.

> **[Permission System](https://docs.agentscope.io/en/versions/2.0.12dev/building-blocks/permission-system/overview.md)**
>
> Fine-grained control over which tools can execute and when.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.