select_none
Deselects all audio in Audacity, clearing any active selection and resetting to no selection.
Instructions
Deselect all audio.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Deselects all audio in Audacity, clearing any active selection and resetting to no selection.
Deselect all audio.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description gives only a three-word summary. It fails to disclose any behavioral traits such as impact on clips, tracks, or undo history.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise at three words, which is appropriate for such a simple action. However, there is no structure beyond a single phrase.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter, no-output tool, the description could still hint at what exactly gets deselected (e.g., entire project vs selected tracks). It is too minimal to be complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so baseline 4 applies. The description adds no parameter info, but none is needed as the schema is complete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Deselect all audio.' clearly states the verb (Deselect) and resource (all audio). It distinguishes from sibling tools like select_all or select_region, but is extremely terse.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like select_all or select_region. The description does not indicate context or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/robworks-code/audacity-mcp-max'
If you have feedback or need assistance with the MCP directory API, please join our Discord server