tdmcp

Connect Ableton Link session

connect_ableton_link_session

Synchronize visual systems to Ableton Link by creating a timing scaffold with beat and bar maps for tempo-locked playback.

Instructions

Create an Ableton Link timing scaffold with beat/bar maps for tempo-locked visual systems.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connect_ableton_link_session"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	ableton_link_session
`active`	No
`signature`	No
`tempo_hint`	No
`export_bars`	No
`parent_path`	No	Parent COMP for the Link scaffold.	/project1
`start_stop_sync`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already indicate it's a mutating, open-world tool. The description adds that it 'creates' a scaffold, but doesn't disclose side effects like whether it modifies existing sessions, network connectivity needs, or what happens to a pre-existing link session. Given annotations cover the safety profile, a baseline 3 is appropriate.

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?

Single concise sentence, front-loaded with the action verb, no wasted words.

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

Completeness2/5

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

For a tool with 7 parameters, no output schema, and low schema coverage, the description is too brief. It doesn't explain the return value, prerequisites, how the scaffold integrates into an Ableton Link setup, or what 'connect' implies vs 'create'. The description leaves significant gaps for an agent to invoke correctly.

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 coverage is only 29% (2/7 params described). The description vaguely mentions 'beat/bar maps' which relates to signature/export_bars but doesn't explicitly explain any of the 7 parameters. With such low schema coverage, the description was expected to compensate but doesn't.

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 ('Create') and resource ('Ableton Link timing scaffold') with a clear scope ('beat/bar maps for tempo-locked visual systems'). It clearly distinguishes itself from generic create tools by specifying the timing domain.

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?

No guidance on when to use this tool versus alternatives like create_tempo_sync or sync_external_clock. It lacks explicit contextual triggers, prerequisites, or exclusions.

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

Deploy Server