Skip to main content
Glama
Sign In
AbletonMCP

AbletonMCP

by juampicosta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_master_volume

Set the master volume of Ableton Live. Accepts values from 0.0 (silent) to 1.0 (0 dB), with boost up to +6 dB.

Instructions

Set master volume. Range: 0.0 (silent) to 1.0 (0 dB). Above 1.0 boosts up to +6dB.

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": {
      "value": "<value>"
    },
    "name": "set_master_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the allowed value range and boosting behavior, but does not mention side effects (e.g., immediate effect, persistence, clipping). This is moderate transparency.

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

Conciseness5/5

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

Two concise sentences, no filler. The main purpose is front-loaded, and the range details are immediately useful. Every sentence earns its place.

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

Completeness4/5

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

For a simple one-parameter tool with an output schema, the description covers purpose and parameter meaning adequately. It could add a note about real-time application or clipping, but is otherwise complete.

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

Parameters4/5

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

The schema has 0% description coverage, so the description must compensate. It explains the 'value' parameter's range (0.0 to 1.0 for attenuation/unity, above 1.0 for up to +6dB boost), adding essential meaning beyond the schema's type-only definition.

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

Purpose5/5

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

The description explicitly states 'Set master volume', using a specific verb and resource. It also provides the range (0.0 to 1.0) and behavior above 1.0, which distinguishes it from sibling volume tools like set_crossfader or set_chain_volume.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus alternatives. It only states the action and range, leaving the agent to infer its usage context.

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