# Execute a specific tool directly

This endpoint allows direct execution of a specific tool with given parameters.

    The tool is executed outside the normal agent conversation flow, allowing users to:
    - Invoke tools programmatically
    - Test tool functionality independently
    - Access tool capabilities without engaging the full agent

    Each tool has different input parameters. Refer to tool documentation for specific input schemas.

    ## Authentication
    Requires API key via x-wabee-access header.

    ## Example Tool Inputs

    Web Search:
    json
    {
        "tool_name": "web_search",
        "tool_input": {
            "query": "Latest market trends in AI"
        }
    }
    

    CSV Search:
    json
    {
        "tool_name": "csv_search",
        "tool_input": {
            "file_path": "data/sales.csv",
            "query": "Find total sales in Q1"
        }
    }

Endpoint: POST /core/v1/tool/execute
Version: v1
Security: APIKeyHeader

## Request fields (application/json):

  - `tool_name` (string, required)
    The name of the tool to execute
    Example: "web_search"

  - `tool_input` (object, required)
    The input parameters for the tool execution
    Example: {"query":"Latest market trends in AI"}

  - `session_id` (any)
    An optional session ID to associate with the tool execution. This can be used to track multiple interactions with tools across different requests.

## Response 200 fields (application/json):

  - `tool_name` (string, required)
    The name of the tool that was executed
    Example: "web_search"

  - `output` (any, required)
    The output from the tool execution
    Example: {"results":["Result 1","Result 2"]}

  - `execution_time` (number, required)
    Time taken to execute the tool in seconds
    Example: 1.25

  - `status` (string, required)
    Status of the tool execution
    Example: "success"

  - `error` (any)
    Error message if the tool execution failed
    Example: "API rate limit exceeded"

## Response 400 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 401 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 403 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 404 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 422 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 500 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available