Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

process_audio_with_plugins

Render an audio file through catalogued plug-ins outside Live to audition settings before committing, then analyze the processed result against the original.

Instructions

Render an audio file through catalogued plug-ins outside Live, to audition settings before committing. chain: [{"plugin": "ValhallaVintageVerb", "params": {"Mix": 25, "Decay": 2.5}}, ...] Values are in the units the plug-in displays (25 = 25 %, 2.5 = 2.5 s, 300 = 300 Hz) or option names; see get_plugin_profile for each parameter's range and units. Then analyse the result with listen_file (optionally against the original).

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": {
      "input_path": "<input_path>",
      "output_path": "<output_path>",
      "chain": "<chain>"
    },
    "name": "process_audio_with_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYes
input_pathYes
output_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say it is a non-destructive, non-open-world write; the description adds the key behavioral facts: rendering happens outside Live, results land at output_path, and parameter values use display units. It omits overwrite behavior for an existing output_path and failure/timeout handling, which matters for a file-writing 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?

Front-loaded with purpose and scope, then the chain format inline as an example rather than prose, then the recommended next step. Dense but every element earns its place; the only mild friction is the example bleeding into the sentence flow.

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?

An output schema exists so return values need no explanation, and the description covers the non-obvious parts: chain structure, units, and the get_plugin_profile dependency. It stops short of stating whether plugins must first appear in the catalog (scan_plugin_catalog) or what happens to a pre-existing output file.

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 carry the load, and it does for the complex parameter: chain is shown as a concrete JSON example with plugin/params keys, plus unit conventions (25 = 25%, 2.5 s, 300 Hz) and a pointer to get_plugin_profile for ranges. input_path and output_path are left unexplained, but their names are largely self-describing.

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 — render an audio file through catalogued plug-ins — and pins the scope with 'outside Live', which separates it from the many in-Live device tools (set_device_param, build_chain, apply_chain_recipe) in the sibling list.

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 clear situational motive ('to audition settings before committing') and a follow-up step ('Then analyse the result with listen_file'). It does not explicitly name when-not to use it or contrast it with build_chain/apply_chain_recipe, so an agent must infer that this is the offline, non-Live path.

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