Skip to main content
Glama

delete_locator

Removes an Ableton locator by exact beat position or by name; if multiple locators share the name, none is removed and their positions are listed. Playback must be stopped.

Instructions

Remove a locator, found by position (exact) or by name. When several locators share the name nothing is removed and their positions are listed. Playback must be stopped.

Parameters:

  • name: Label of the locator

  • time: Its song position in beats (wins over name)

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": "delete_locator"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
timeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses that the operation is destructive, that an ambiguous name results in a no-op with positions listed, and that 'time' takes precedence over 'name'. It stops short of stating auth/permission needs or what happens when no locator matches, which keeps it out of the top band.

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?

Front-loaded with the core action and resolution order, followed by a compact edge-case sentence and a short parameter block. Every sentence adds new information; nothing is wasted or buried.

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 two-optional-parameter deletion tool with an output schema present, the description covers the precondition, the disambiguation behavior, and parameter precedence. Only the failure case for a non-matching locator is unaddressed, which is a small residual gap.

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 0%, so the description must compensate, and it does: 'name' is defined as the label, 'time' as song position in beats, and the crucial precedence semantics ('wins over name') are supplied nowhere in the schema. Only the exact-vs-nearest matching nuance of 'time' is left slightly underspecified.

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?

States a specific verb and resource ('Remove a locator') and immediately explains the two resolution strategies (exact position or name). An agent can tell this apart from create_locator or any of the clip/scene deletion siblings without opening the schema.

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?

Gives a hard precondition ('Playback must be stopped') and a precedence rule ('time ... wins over name'), plus the ambiguity fallback when a name matches multiple locators. It does not name alternative tools or say when not to use it, but the resource is distinct enough that this is a minor gap.

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