openDAW MCP

mcp_opendaw_get_region_play_mode

Read-only

Get play mode details for an audio region: stretch type, playback rate, cents, and transient mode. Use unit, track, and region indices to retrieve the information.

Instructions

Get the play mode of an audio region — stretch type, playback rate, cents, transient mode.

unit_index: AU index. track_index: Track index within the AU. region_index: Audio region index.

Returns play mode details, or info if no stretch mode (plain playback).

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": {
      "unit_index": "<unit_index>",
      "track_index": "<track_index>",
      "region_index": "<region_index>"
    },
    "name": "mcp_opendaw_get_region_play_mode"
  }
}

Input Schema

Name	Required	Description	Default
`unit_index`	Yes
`track_index`	Yes
`region_index`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.386.0Aug 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With readOnlyHint=true already present in annotations, the description adds meaningful behavioral context by disclosing the fallback behavior ('or info if no stretch mode (plain playback)') and enumerating the returned fields. This goes beyond the annotation's simple safety hint.

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?

The description is compact and well-structured: a one-sentence purpose statement, a bullet-like list of parameter definitions, and a return-behavior sentence. Every sentence earns its place with no redundancy.

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?

For a simple read-only getter with three integer parameters and an output schema present, the description covers purpose, parameter semantics, and return behavior including the edge case of no stretch mode. No critical information is missing for an agent to invoke it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by defining all three parameters (unit_index, track_index, region_index) with clear hierarchical context (AU, track within AU, audio region). This adds substantial meaning beyond the bare integer type in the schema.

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 uses a specific verb ('Get') and resource ('play mode of an audio region'), and explicitly lists the returned fields (stretch type, playback rate, cents, transient mode). This clearly distinguishes it from sibling getter tools like get_region_info or get_track_info.

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 implies its usage by naming the resource and parameters, but provides no explicit guidance on when to prefer this tool over alternatives, nor any exclusions or prerequisite conditions. Usage context is inferred rather than stated.

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

Deploy Server