Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

run_batch

Destructive

Execute multiple tool steps in a single call so one undo reverts the entire batch, with optional stop_on_error to halt at the first failure.

Instructions

Run several tools in one call as ONE undo step in Live (one Ctrl+Z reverts them all). steps: [{"tool": "create_midi_track", "args": {"index": -1}}, {"tool": "set_track_name", "args": {"track_index": 3, "name": "Pad"}}, ...]. Results come back in order; with stop_on_error the batch stops at the first failure (earlier steps stay applied — call undo once to revert the batch). Desktop, export and analysis tools can't be batched.

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": {
      "steps": "<steps>"
    },
    "name": "run_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYes
stop_on_errorNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the atomic-undo model, ordered result return, and the stop_on_error failure semantics including the partial-application caveat and the remedy (call undo once). This is exactly the behavioral context an agent needs before invoking a destructiveHint=true 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?

Dense and front-loaded with the key undo-grouping benefit, with no filler sentences. The inline JSON example and line wrapping make it slightly harder to scan, but nothing is wasted.

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?

Covers the mechanics an agent needs for a two-parameter batching tool, and an output schema exists so return values need not be described. Minor gaps: whether batches can nest, size limits, and how args are validated against each target tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema is an untyped array of objects, so the description carries the full burden — it supplies the concrete step shape with tool/args keys and an example. It also explains stop_on_error's effect on partial application, which the schema only declares as a defaulted boolean.

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 ('Run several tools in one call') plus the distinguishing outcome ('ONE undo step in Live'). This separates it cleanly from sibling tools like undo/redo and from calling individual tools directly.

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 an explicit exclusion ('Desktop, export and analysis tools can't be batched') and implies usage for grouping multi-step edits under a single undo. It does not spell out when to prefer a batch over sequential individual calls beyond the undo-benefit framing.

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