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

# Custom tools

> Give your agents new abilities: call your own systems over HTTP, or look up your catalogue, orders and contacts.

Custom tools let an agent do something the built-in tools can't, such as checking stock in your own system, looking up an order status, or searching your catalogue in a specific way. Only **enabled** tools reach the agents.

Open them from **Build → Custom tools**.

![The Custom tools page with an enabled check\_unit\_availability tool](https://mintcdn.com/magicwebs/lXS3DuVdQz1WpiFT/images/console/custom-tools.png?fit=max\&auto=format\&n=lXS3DuVdQz1WpiFT\&q=85\&s=737aa7d4ecc58a595aea66add7f8d1b1)

## Create a tool from a task

The quickest way is to describe the job in plain words.

![Build a tool from a task description](https://mintcdn.com/magicwebs/lXS3DuVdQz1WpiFT/images/console/custom-tools-create.png?fit=max\&auto=format\&n=lXS3DuVdQz1WpiFT\&q=85\&s=581b691ebdf0ad733f5bae2a949c039a)

1. Choose **Create from a task**.
2. Describe **The task**, for example "Check if a unit type is still available in a project".
3. Optionally add **API details**: an endpoint, a curl command or a link to the docs.
4. Choose who it is **Available to**: every agent, or one.
5. Choose **Design the tool**. Turn on **Enable immediately** to use it straight away; otherwise it is saved as a draft for you to review.

## Create a tool by hand

Choose **Manual** and fill in:

| Field | Notes |
| - | - |
| **Display name** | Shown in the console |
| **Tool name** | A short `snake_case` name, fixed once created |
| **Description the model reads** | What the tool does and when to use it. This is what decides whether the agent calls it |
| **When to use it** | Extra guidance for the agent |
| **Kind** | **HTTP request** to your own system, or **Workspace data query** over products, orders or contacts |
| **Parameters** | What the agent must fill in: name, type, required, description, fixed choices |
| **Status** | Draft (not given to the agent), Enabled or Disabled |

For an **HTTP request**, set the method and URL (use `{{parameter}}` placeholders), headers and request body. For a **data query**, choose the table, the search parameter and a row limit.

> [!TIP]
>
> Write the description as "what this does and when to use it". The demo's tool reads: "Look up which homes and units are in the catalogue and their availability notes. Use when a customer asks whether a type of unit is still available."

Each tool card shows its status, kind, the agents it is scoped to and how often it has been called. Use the switch to enable or disable it. Tools added by an integration say **Managed by …**.


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