Adjust a track's volume level in decibels by specifying the track index and desired volume value, with a range from -150 dB to +12 dB.
Set track volume in dB. Range: roughly -150 to +12 dB.
| Name | Required | Description | Default |
|---|---|---|---|
| volume_db | Yes | ||
| track_index | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only mentions the volume range, omitting that this is a mutation operation, potential effects on automation, or permissions needed. The transparency is minimal.
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 concise with two sentences, no extraneous words. However, it could be structured to include more essential details without losing brevity.
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?
Given no output schema and no parameter descriptions, the description is too sparse. It does not explain return values, validation, or typical usage patterns, leaving the agent underinformed.
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?
Schema description coverage is 0%, so the description should clarify parameter meaning. It does not explain track_index (e.g., 0-based or 1-based) or volume_db (e.g., 0 dB = unity). No added value beyond the schema.
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 clearly states the action 'Set track volume' and includes the unit (dB) and range, distinguishing this tool from siblings like set_master_volume or set_send_volume. However, it could be more explicit about the target being an individual track.
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 is provided on when to use this tool vs alternatives (e.g., set_master_volume) or prerequisites (e.g., track must exist). The description lacks usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.