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

# How do I add a new tool to a specific provider?

> Step-by-step instructions on creating and registering a new actionable tool under an API Provider in HasMCP.

# Adding a New Tool to a Provider

## Using HasMCP UI

<img src="https://mintcdn.com/hasmcp/9Embd1XJnDsV9Wi6/images/kb/create-provider-tool.png?fit=max&auto=format&n=9Embd1XJnDsV9Wi6&q=85&s=fee9536922e8fd37274380bce6d15c41" alt="Create Provider Tool Modal" width="2560" height="1440" data-path="images/kb/create-provider-tool.png" />

The visual dashboard allows you to define complex tools natively:

1. Navigate to the specific **Provider Details** page.
2. In the "Tools" tab or section, click the **Add Tool** button.
3. Define the tool's `name`, `description`, and construct its `inputSchema` (JSON Schema format) that the LLM will use to invoke it.
4. Specify the execution path (e.g., `/v1/users/{user_id}`).
5. Click **Create** to bind the new capability to the provider.

## Using REST API

To declare a new tool programmatically so that your MCP servers can leverage it, you post a `ProviderToolCreate` JSON object to a specific provider's tool collection.

### The Endpoint

**`POST /providers/{providerId}/tools`**

*(Note: Replace `{providerId}` with the 11-character ID of the parent provider).*

### JSON Payload Requirements

Your payload must include a `tool` object containing:

* **`name`** (string): A distinct, programmatic name for the tool (e.g., `get_user_billing`).
* **`description`** (string): Precise instructions to the LLM explaining exactly what this tool does and when to call it.
* **`method`** (string): The HTTP method (e.g., `GET`, `POST`).
* **`path`** (string): The execution path routing logic.
* **`reqBodyJSONSchema`** (object): JSON Schema for the body parameters.
* **`queryArgsJSONSchema`** (object): JSON Schema for the query arguments.
* **`pathArgsJSONSchema`** (object): JSON Schema for the path arguments.

### Example cURL Request

```bash theme={null}
curl -X POST https://app.hasmcp.com/api/v1/providers/kSuB9Gf6aD4/tools \
 -H "Authorization: Bearer YOUR_TOKEN" \
 -H "Content-Type: application/json" \
 -d '{
 "tool": {
 "name": "lookupCustomer",
 "description": "Searches the CRM for a customer by email address.",
 "queryArgsJSONSchema": {
   "type": "object",
   "properties": {
     "email": { "type": "string" }
   },
   "required": ["email"]
 },
 "method": "GET",
 "path": "/api/v2/customers/search"
 }
 }'
```