---
title: "Let an app's AI use its tools"
method: PUT
path: "/client/mcp/apps/{id}/ai-tools"
tags: ["Tool gateway"]
---

# Let an app's AI use its tools

`PUT /client/mcp/apps/{id}/ai-tools`

## Request

- Base URL: `https://api.roar-ai.com`
- URL: `https://api.roar-ai.com/client/mcp/apps/{id}/ai-tools`
- Auth: HTTP bearer

Body `{"enabled": true}` makes Roar add your company's tools to this app's own `/v1/chat/completions` requests that send no tools of their own, so the app gets the tools its key is given without a code change. Each such request then carries the tools' descriptions, which it is billed for. `{id}` is the app's web service. The same people who may give the app tools may change it; turning it ON takes a person signed in to the console (403 for a key), and a key may only turn it off.

## Path parameters

- `id` string, uuid, required

## Request body

- object
  - `enabled` boolean, required

## Response `200`

The setting

- AppAiTools
  - `enabled` boolean, required

## Other responses

- `403`: Not allowed to turn it on
- `404`: No such app

---

[API](https://skmtc.dev/roar-ai/apis/roar-ai-api.md) · [All operations](https://skmtc.dev/roar-ai/apis/roar-ai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/roar-ai/apis/roar-ai-api/revisions/37e4d0d5a7fe?raw)
