Skip to main content
Glama

create_locator

Places or renames a named locator at a specified beat in the Arrangement to mark song sections; stop playback before use.

Instructions

Put a named locator in the Arrangement. A locator already at that beat is renamed rather than removed. Playback must be stopped.

Parameters:

  • name: Label shown in Live ("Intro", "Drop", "Break"...)

  • time: Song position in beats

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": {
      "name": "<name>",
      "time": "<time>"
    },
    "name": "create_locator"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
timeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/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 it does disclose two meaningful traits: an existing locator at that beat is renamed rather than removed, and playback must be stopped first. It does not say what is returned, whether renaming preserves other locator properties, or what happens on invalid beat positions, leaving notable gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences followed by a compact parameter list; the behavior and precondition are front-loaded and nothing is padded. The 'Parameters:' heading adds light structure at negligible cost.

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-parameter mutation tool with an output schema (so return values need not be explained), the description covers intent, the key overwrite semantic, the playback precondition, and parameter units. Only the failure mode when playback is active and any rename side effects remain unstated.

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 0%, and the description does partially compensate: it gives the unit for time ('Song position in beats') and illustrates name with concrete Live examples ('Intro', 'Drop', 'Break'). That is genuinely useful beyond the bare schema, though neither parameter's type constraints or valid ranges are addressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource — 'Put a named locator in the Arrangement' — and the rename-not-remove clause makes clear it is an upsert-style creation rather than a plain add. It does not explicitly contrast with the sibling delete_locator, but the operation is unambiguous.

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?

One real precondition is given: 'Playback must be stopped.' That is valuable operational guidance, but there is no statement of when to reach for this versus delete_locator or other arrangement tools, and no error behavior if playback is running.

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