Skip to main content
Glama
Sign In
ableton-mind

ableton-mind

by Pantani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

track_set_volume

Set a regular track's mixer volume using a normalized value (0 to 1). Ideal for adjusting mix balance after verifying the track index, with idempotent updates and confirmation of before and after levels.

Instructions

Set a regular track's mixer volume as a normalized 0..1 value. Use for mix balance changes after confirming the track index. Idempotent within 1e-4; returns linear and dB before/after values with verification diff on mismatch.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "index": "<index>",
      "volume": "<volume>"
    },
    "name": "track_set_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes
volumeYesNormalized 0..1 per ADR-0004.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses idempotence within 1e-4, return of before/after linear and dB values, and verification diff on mismatch. This is good transparency for a volume setter, though permissions and side effects are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with action and value range. No wasted words, though the second sentence could be slightly rephrased for clarity. Efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks output schema but mentions return values. Does not address error handling (e.g., invalid index) or state changes. For a simple setter, this is minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 50% of parameters (volume has description). The description adds no extra parameter details beyond 'normalized 0..1', which is already in schema. Index parameter lacks description in both schema and tool description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool sets a regular track's mixer volume as a normalized 0..1 value. This distinguishes it from sibling tools for naming, tempo, etc. However, 'regular track' is slightly ambiguous (excludes master?).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises using after confirming the track index, providing minimal usage context. No explicit when-not or alternatives to other volume-related tools, but the sibling list lacks similar volume tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools