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

# Tools

> Learn how 0mcp turns your API operations into MCP tools.

A **tool** is an action that an MCP client can invoke.

In 0mcp, each tool is generated from an API operation in your [**OpenAPI** specification](/api-sources/openapi). When you import your API, 0mcp automatically creates a tool for every available operation, allowing AI clients to interact with your API through the Model Context Protocol.

For example:

| API operation      | Generated tool  |
| ------------------ | --------------- |
| `GET /orders/{id}` | `get_order`     |
| `POST /tickets`    | `create_ticket` |
| `GET /users`       | `list_users`    |

## What's included in a tool?

Every generated tool contains the information needed for an AI client to use it, including:

* Name
* Description
* HTTP method
* API path
* Parameters
* Request body schema
* Response schema
* Authentication requirements

AI clients use the tool's name and description to decide which action to invoke, so clear and descriptive metadata leads to better tool selection.

## Managing tools

From the **Tools** page, you can customize how each tool behaves without changing your API.

You can:

* Rename the tool
* Edit its description
* Enable or disable it
* Review its inputs and request body
* Configure [authentication](/concepts/authentication-model)
* Set request timeout
* Limit maximum response size
* Allow or block HTTP redirects

These settings only affect how the tool is exposed through your MCP server. They never modify your upstream API.

## Best practices

* Use clear, action-oriented names such as `get_order`, `list_customers`, or `create_ticket`.
* Write descriptions that explain **when** the tool should be used, not just what endpoint it calls.
* Disable operations you don't want AI clients to access.
* Carefully review destructive operations such as deleting resources or processing payments before exposing them.

<Warning>
  Test tools that create, update, delete, send, or charge data with limited credentials before exposing them to production clients.
</Warning>

## Publishing changes

Changes to tools are first saved as a **draft**.

Connected MCP clients continue using the current published version until you [publish a new one](/guides/versioning). Before publishing, use the [**Playground**](/guides/playground) to verify that your tools behave as expected.