Skip to main content
Glama

Sync external clock (tempo)

sync_external_clock

Sync the global tempo to a live source: tap by ear, join an Ableton Link session, or receive MIDI clock. Ensures beat-synced visuals follow the music.

Instructions

Lock the project tempo to a live source so beat-synced visuals follow the music. mode picks the source: 'tap' (default) gives a Bpm knob + Tap pulse you dial/tap by ear; 'ableton_link' locks to an Ableton Link session on the network; 'midi_clock' derives BPM from incoming MIDI timing-clock (24 PPQN). All modes write the global tempo (op('/').time.tempo), so create_tempo_sync clocks and create_autopilot follow. The Link/MIDI modes are hardware-gated — without that source present the manual Bpm knob still drives the clock.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNoStarting tempo in BPM (match the DJ's displayed BPM, then fine-tune by tapping).
modeNoHow the tempo is sourced. 'tap' (default): a Bpm knob + Tap pulse you dial/tap by ear. 'ableton_link': lock to an Ableton Link session on the network (an Ableton Link CHOP's tempo drives the clock). 'midi_clock': derive BPM from incoming MIDI timing-clock (24 PPQN). The Link/MIDI modes need that source present on the machine — without it they fall back to the manual Bpm knob.tap
parent_pathNoParent COMP path the self-contained 'tempo_clock' container is created inside./project1
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds that 'All modes write the global tempo (op('/').time.tempo)' and explains fallback behavior for absent sources. This provides useful behavioral context beyond annotations, such as the side-effect on global tempo and how other tools depend on it. No contradictions.

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 two sentences long, covering purpose, mode details, side-effects, and fail-safes without redundancy. Every sentence adds essential information, making it highly efficient and front-loaded.

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?

Given the tool's moderate complexity (3 params, 3 modes, no output schema), the description covers purpose, all modes with dependencies, side-effects, and relationship to other tools. It could mention the container creation more explicitly, but overall it is sufficient for an agent to select and invoke correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds practical guidance for 'bpm' ('match the DJ's displayed BPM, then fine-tune by tapping') and clarifies 'mode' options with context about source availability. This adds value beyond the schema descriptions.

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 the tool's purpose: 'Lock the project tempo to a live source so beat-synced visuals follow the music.' It identifies the verb 'lock', the resource 'project tempo', and the context. It distinguishes from sibling tools like 'create_tempo_sync' by noting that this tool writes the global tempo and others follow.

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

Usage Guidelines4/5

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

The description indicates when to use the tool to sync to a live source and mentions that 'create_tempo_sync clocks and create_autopilot follow' implying a hierarchy. It also explains hardware gating for Link/MIDI modes and fallback behavior, providing clear usage context. However, it does not explicitly state when not to use it or alternative tools.

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/Pantani/tdmcp'

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