Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apply_chain_recipe

Destructive

Build a ready-dialled device chain from Live's stock devices for vocals, piano, strings, bass, drums, or master, with every parameter set on any machine.

Instructions

Build a ready-dialled chain from Live's own devices (works on any machine, every parameter set): vocal_pop (EQ Eight HPF + presence, Compressor 3:1, de-ess, Glue), piano_ballad (gentle HPF, warm low-mid dip, light compression), strings_pad (HPF, air, wide), cello_solo, bass_warm, drums_soft, master_soft (gentle glue, EQ tilt, limiter at -1 dB).

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>",
      "recipe": "<recipe>"
    },
    "name": "apply_chain_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipeYes
track_typeNotrack
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is partly covered. The description adds that chains are built from Live's own devices, but it does not say whether an existing chain is replaced, what happens to current devices, or what track_type actually controls for this destructive operation.

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?

The description is compact and front-loaded with the core action, followed by a useful recipe list. The parenthetical recipe details are dense but still readable and mostly earn their place.

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?

This is a destructive track-mutating tool with three parameters and no schema descriptions, so the description should clarify targeting, existing-device impact, and recipe selection. It provides recipe names but leaves the operational effects and two of three parameters underexplained, despite having an output schema that covers return values.

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 parameter meaning. It names recipe values like vocal_pop and piano_ballad, which helps for the recipe parameter, but it does not explain track_index or track_type, nor does it formally state that recipe accepts exactly those listed names.

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: "Build a ready-dialled chain" from Live's own devices, and it lists concrete recipe names. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like build_chain or add_effect.

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?

Usage is implied by the recipe list and the note that it works on any machine with every parameter set. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative such as build_chain for custom chains.

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