Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_warp_marker

Adds a warp marker at a specified beat to pin audio in a track clip to a sample time or its current playback position.

Instructions

Add a warp marker at beat_time (pinning the audio at sample_time seconds, or where it currently plays).

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": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>",
      "beat_time": "<beat_time>"
    },
    "name": "add_warp_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
beat_timeYes
clip_indexYes
arrangementNo
sample_timeNo
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description usefully adds the fallback behavior when sample_time is omitted ('or where it currently plays'), but says nothing about effects on existing markers, warp mode requirements, or failure conditions.

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?

A single front-loaded sentence with the key parameter semantics parenthesized; nothing extraneous. The parenthetical is slightly dense but earns its place.

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

Completeness3/5

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

The description is adequate for a clip-level mutation and the output schema covers return values. However, with zero schema description coverage and three unexplained parameters, plus no mention of warp prerequisites, it does not fully equip an agent to call this 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 description coverage is 0%, so the description must carry the parameter burden. It explains beat_time and the sample_time-or-current-position behavior, but leaves track_index, clip_index, and the arrangement boolean completely undocumented in both schema and description.

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 ('Add a warp marker') and names the beat_time/sample_time semantics, so the agent knows exactly what operation is performed. It does not distinguish itself from sibling tools like get_warp_markers, move_warp_marker, or remove_warp_marker, which keeps it below a 5.

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?

There is no guidance on when to use this tool versus its siblings (get/move/remove warp marker), nor on prerequisites such as warp being enabled or the clip being audio. The usage context is only inferable from the parameter names.

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