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

# Configure the tools

> Edit and test the tools that make up your MCP: parameters, authentication, methods, and endpoints.

## Overview

Once your MCP has been created or imported, you can adjust the behavior of each **tool** from the configuration panel.\
Each tool represents an endpoint of your API and defines how the model will interact with it.

<img src="https://mintcdn.com/devic/CbfJRSI_zfJsoSsX/Tool-description.png?fit=max&auto=format&n=CbfJRSI_zfJsoSsX&q=85&s=7be58ea23c562b01354a651e53761dc7" alt="Tool configuration view" width="1915" height="983" data-path="Tool-description.png" />

***

## Configuration Editor

When selecting a tool, the **editor** opens, where you can define the following fields:

* **Function name:** internal function name.
* **Description:** brief explanation of the tool’s purpose (example: “Retrieves studies categorized by type within a date range”).
* **Parameters:** parameters required by the API (name, type, and description).
* **Endpoint:** service path (`/api/analytics/studies/counts-by-type`, for example).
* **Method:** HTTP method used (GET, POST, PUT, DELETE).

<Card title="Automatic property detection" icon="wand-magic-sparkles" horizontal>
  Devic automatically detects parameters defined in the JSON and displays them as <strong>Detected Properties</strong>,
  ready to bind with the body or endpoint path.
</Card>

<img src="https://mintcdn.com/devic/CbfJRSI_zfJsoSsX/tool-configuration.png?fit=max&auto=format&n=CbfJRSI_zfJsoSsX&q=85&s=53f310bf2fe1ba6fd5dc782ba7a6e35b" alt="Parameters and detected properties" width="1915" height="983" data-path="tool-configuration.png" />

***

## Editing modes

You can define a tool in two ways:

* **Form:** visual interface with editable fields for each property.
* **JSON:** structured view of the full schema, compatible with OpenAPI.

The **Generate** button converts the parameters defined in Form mode into their JSON equivalent.

<img src="https://mintcdn.com/devic/CbfJRSI_zfJsoSsX/form-json-generate.png?fit=max&auto=format&n=CbfJRSI_zfJsoSsX&q=85&s=789c783b0c5db274a10eca044e168625" alt="JSON mode view" width="1915" height="983" data-path="form-json-generate.png" />

***

## Advanced options

At the bottom of the panel, you’ll find additional settings:

* **Query Parameters:** parameters sent via URL (`?param=value`).
* **Path Parameters:** variables included in the route (`/api/{id}/data`).
* **Body Property Key:** main property of the JSON body.
* **Custom Headers:** custom headers for authentication or context.
* **Widget Binding:** links the tool with embedded widgets or SDKs.

<Card title="Save configuration" icon="floppy-disk" horizontal>
  Click <strong>Confirm</strong> to validate the changes and <strong>Save Changes</strong> to apply them to the MCP.
</Card>

<img src="https://mintcdn.com/devic/CbfJRSI_zfJsoSsX/query-parameters-path-parameters-body-property-key-custom-headers-widget-binding.png?fit=max&auto=format&n=CbfJRSI_zfJsoSsX&q=85&s=f6eff217402390713b095806ddcafede" alt="Advanced options and saving" width="1915" height="983" data-path="query-parameters-path-parameters-body-property-key-custom-headers-widget-binding.png" />

***

## Validation and testing

Once the tool is configured, the MCP will be ready for use.\
You can test its execution from agents or assistants, or verify it in the **Tool Calls** tab, where all invocations are recorded.

***

<Card title="Next step" icon="bullhorn" href="/devic/mcps/my-mcps/publish">
  Learn how to publish your MCP so it becomes available to internal agents or external environments.
</Card>