Skip to main content
Glama

set_return_device_parameter

Idempotent

Set a parameter on a device in a return track. Use return index, device index, parameter name/index, and a value within its native range; values are clamped.

Instructions

Set one enabled parameter on a device in a return track's chain.

Call get_return_device_parameters first and use its parameter name/index and native min/max; out-of-range values are clamped. Use set_device_parameter for a regular track or set_master_device_parameter for the full-mix chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesValue in the parameter's native range; the server clamps it to the min/max reported by the matching get_*_device_parameters tool.
parameterYesParameter name or zero-based parameter index returned by the matching get_*_device_parameters tool.
device_indexYesZero-based device position in the target track's device chain.
return_indexYesZero-based return-track index; 0 is Return A.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Adds clamping behavior and prerequisite beyond annotations which already indicate idempotent and non-destructive.

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 sentences, front-loaded with action, then context and alternatives; no wasted words.

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

Completeness5/5

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

With full schema coverage, output schema, and annotations, the description covers prerequisites, alternatives, and behavior adequately.

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

Parameters3/5

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

Schema coverage is 100% and description adds minimal extra meaning; clamping is already in schema value description.

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?

Clearly states it sets a parameter on a device in a return track's chain, and distinguishes from siblings like set_device_parameter and set_master_device_parameter.

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

Usage Guidelines5/5

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

Explicitly says to call get_return_device_parameters first and names alternative tools for other track types.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wstierhout/ableton-live-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server