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

# Tool sounds

> Prepare stored sound and timing preferences for tool calls while sound previews and live playback remain planned.

A tool sound is intended to indicate a wait while an action is in progress. Choose whether it would help the listener understand the pause before selecting a sound.

<Note>
  Tool sound preferences can be saved, but the current webhook editor has no supplied sound-preview assets. A disabled preview control is not playable audio. Live conversation playback and timing remain unverified and unavailable through this guide.
</Note>

## Review the stored preferences

| Field | Authoring values |
| - | - |
| `tool_call_sound` | `null`, `typing`, `elevator1`, `elevator2`, `elevator3`, or `elevator4`. |
| `tool_call_sound_behavior` | `auto` or `always`; default `auto`. |
| `pre_tool_speech` | `auto`, `force`, or `off`; default `auto`. |

The intended behavior of `auto` is to associate the sound with pre-tool speech; `always` requests it for every invocation. These are requested settings, not evidence that playback occurred.

## Prepare a sound preference

<Steps>
  <Step title="Open an existing webhook tool">
    Use the signed-in [Tools dashboard](https://threetone.in/app/agents/tools). Open **Advanced**, then review **Tool call sound**. Personal API keys cannot manage these tool resources.
  </Step>

  <Step title="Choose whether a sound is appropriate">
    Select **None** for `null`, or one of the listed presets. Consider whether an extra sound would compete with spoken instructions or accessibility needs. Do not upload a custom track through an invented sound field.
  </Step>

  <Step title="Review timing and save">
    When a sound is selected, review **Sound behavior**: **With pre-speech** maps to `auto`, and **Always play** maps to `always`. Save the tool, reopen it, and check the persisted values. Keep actual listening and timing verification pending.
  </Step>
</Steps>

MCP per-tool overrides have a distinct convention: `tool_call_sound: "off"` requests silence, while `null` means inherit the server setting. Do not put `"off"` in an ordinary webhook or client tool's sound field.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does a sound indicate that the action succeeded?" id="faq-tool-sounds-result">
    No. A progress cue is separate from the tool's result. Confirm completion from the action's actual response when a supported execution path is available.
  </Accordion>

  <Accordion title="Is this the conversation's background audio?" id="faq-tool-sounds-background">
    No. [Audio environment](/agents-platform/configure/voice-and-language/audio-environment) describes separate background-sound settings. Neither configuration proves live playback.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.