> ## Documentation Index > Fetch the complete documentation index at: https://docs.support.onclarity.com/llms.txt > Use this file to discover all available pages before exploring further. # Set an agent's tools > Replaces the agent's whole tool set; the array order becomes the attachment order. A tool left out is detached, not deleted. Each id must be a project-wide tool or a tool private to this agent. The change goes to the agent's draft; live calls get it when the agent is published. ## OpenAPI ````yaml api-reference/voice-openapi.json PUT /v1/projects/{projectId}/agents/{id}/tools openapi: 3.0.3 info: title: Clarity Voice API version: '1.0' description: >- Voice agents and their tools, outbound calls, conversations, campaigns, telephony, and evals. servers: - url: https://voice-api.onclarity.com security: - organizationApiKey: [] tags: - name: Projects description: >- The projects your organization owns. Every other resource lives in a project. - name: Agents description: Create, configure, version and publish voice agents. - name: Outbound calls description: Have a published agent phone a number now. - name: Conversations description: >- One record per call session, with its calls, recordings, transcripts and artifacts. - name: Calls description: The calls of a project, with their status, direction, timing and outcome. - name: Campaigns description: Outbound calling campaigns that phone a list of numbers on a schedule. - name: Eval suites description: >- Reusable sets of eval scenarios and test cases to measure an agent against. - name: Eval judges description: The LLM judges that score eval calls against your test cases. - name: Eval scenarios description: The simulated-caller scenarios of your eval suites. - name: Eval test cases description: The checks a judge applies to each eval call. - name: Eval submissions description: Run an eval suite against an agent and read the verdicts. - name: Phone numbers description: >- The phone numbers of a project, where their calls come from, and how agents call out from them. - name: Inbound SIP trunks description: Bring calls from your own SIP infrastructure to Clarity agents. - name: Outbound SIP trunks description: >- The SIP endpoints Clarity dials through for outbound calls from your numbers. - name: Tools description: The tools agents call during a conversation, and which agents use them. paths: /v1/projects/{projectId}/agents/{id}/tools: parameters: - $ref: '#/components/parameters/ProjectIdPath' - $ref: '#/components/parameters/AgentId' put: tags: - Tools summary: Set an agent's tools description: >- Replaces the agent's whole tool set; the array order becomes the attachment order. A tool left out is detached, not deleted. Each id must be a project-wide tool or a tool private to this agent. The change goes to the agent's draft; live calls get it when the agent is published. operationId: setAgentTools requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PutAgentToolsRequest' example: tool_ids: - 1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d - 6e2a4c8d-1b3f-4a5c-9d7e-0f1a2b3c4d5e responses: '200': description: The agent's tools were replaced. content: application/json: schema: type: object required: - success - message properties: success: type: boolean message: type: string example: success: true message: Agent tools updated '400': description: >- A tool id is unknown, or private to another agent (`code: invalid_tool_scope`, with the ids in `tool_ids`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: >- Tool(s) "lookup_account" are private to another agent and cannot be attached. code: invalid_tool_scope tool_ids: - 9f8e7d6c-5b4a-4c3d-8e2f-1a0b9c8d7e6f '401': $ref: '#/components/responses/Unauthorized' '403': description: Your credential has no administrative access to the project. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: The project or the agent does not exist. content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: >- The body failed validation (`tool_ids` missing or holding the same id twice), the agent is a Voice Assist agent, which has no tools (`code: NOT_APPLICABLE_TO_AGENT_TYPE`), a newly attached tool is no longer offered to voice agents (`error: channel_not_allowed`), or the tools would no longer fit the agent's model context (`code: AGENT_BASELINE_EXCEEDS_CONTEXT`). content: application/json: schema: $ref: '#/components/schemas/ValidationError' example: error: 'tool_ids: tool_ids must not contain duplicates' issues: - path: tool_ids code: custom message: tool_ids must not contain duplicates components: parameters: ProjectIdPath: name: projectId in: path required: true schema: type: string description: Project id AgentId: name: id in: path required: true schema: type: string description: Agent id schemas: PutAgentToolsRequest: type: object required: - tool_ids description: Fields not listed here are ignored. properties: tool_ids: type: array uniqueItems: true items: type: string description: >- The agent's whole tool set, in attachment order: project-wide tools and tools private to this agent. `[]` detaches every tool. Error: type: object required: - error additionalProperties: true properties: error: type: string description: Error message code: type: string description: >- A stable machine-readable reason, present on the refusals a client may branch on. Among them: `PUBLISH_CAPABILITY_REQUIRED` (403, the credential may not change what is live), `AGENT_NOT_PUBLISHED` (409, the agent has no published version yet), `AGENT_TYPE_NOT_DISPATCHABLE` (422, a Voice Assist agent named where an agent must place a call or answer one itself — a campaign, an outbound caller ID, a dispatched call, an eval; a number's inbound dispatch rule accepts one; the body carries `agent_type` and `agent_id`), `ASSIST_FLEET_NOT_CONFIGURED` (422 on a dispatch rule naming a Voice Assist agent in a project whose LiveKit has no Voice Assist listener), `NOT_APPLICABLE_TO_AGENT_TYPE` (422, a voice-only setting written on a Voice Assist agent), `AGENT_TYPE_BOUNDARY` (409), `AGENT_TYPE_NOT_SUPPORTED` (400), `INVALID_CUSTOMER_TIMEZONE` (400, `customer_timezone` is not a time zone name; the body carries the value), `VOICE_ASSISTANT_REQUIRED` (403, the organization is not licensed for Voice Assist), `ORGANIZATION_UNAVAILABLE` (503), `REGION_PROFILE_CONFLICT` (503), `LLM_SERVICE_TIER_UNAVAILABLE` (422, an agent's processing speed is not offered by its model or not enabled for the organization; `reason` says which) and `AUTH_UPSTREAM_UNAVAILABLE` (503 on any endpoint, with `Retry-After`: the credential could not be checked right now; it was not rejected and the request was not carried out). ValidationError: type: object description: >- A validation failure. `error` is a human-readable summary; `issues` (request validation) or `details` (agent configuration validation) locate each problem. A refused processing speed answers with `error` and `code` both `LLM_SERVICE_TIER_UNAVAILABLE` and the fields `path`, `reason`, `tier`, `provider` and `model`. properties: error: type: string code: type: string description: >- A machine-readable code, on the failures that carry one: `LLM_SERVICE_TIER_UNAVAILABLE` for a processing speed the agent cannot use. message: type: string path: type: string description: >- With `LLM_SERVICE_TIER_UNAVAILABLE`: the refused field, `agent_model_config.llm_service_tier`. reason: type: string enum: - model - organization description: >- With `LLM_SERVICE_TIER_UNAVAILABLE`: `model` when the language model does not offer the speed (or the value is not a speed at all), `organization` when your organization does not have it. tier: type: string description: With `LLM_SERVICE_TIER_UNAVAILABLE`, the refused value, as text. provider: type: string description: >- With `LLM_SERVICE_TIER_UNAVAILABLE`, the agent's language model provider. model: type: string description: With `LLM_SERVICE_TIER_UNAVAILABLE`, the agent's language model. issues: type: array items: type: object properties: path: type: string description: Dotted path of the offending field code: type: string message: type: string details: type: array items: {} responses: Unauthorized: description: >- No credential was sent, or the API key is invalid or revoked. A key that could not be checked at all answers 503 `AUTH_UPSTREAM_UNAVAILABLE` instead (see Errors). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Invalid or revoked token securitySchemes: organizationApiKey: type: http scheme: bearer description: >- Your organization API key (it starts with `anek_org_`). The same key works on the Voice API and the Support API. See [Authentication](/authentication). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.