Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_plugin_preset

Destructive

Switch a plug-in to an exposed preset by fuzzy name or index, letting you change a device's sound without manually browsing preset lists.

Instructions

Switch a plug-in to one of its exposed presets, by (fuzzy) name or index.

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>",
      "preset": "<preset>"
    },
    "name": "set_plugin_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYes
track_typeNotrack
device_nameNo
track_indexYes
device_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/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, but the description adds nothing about what is destroyed (the current preset/device state) or whether the change is undoable. It also says nothing about how the target device is resolved when device_name and device_index are both null, which is the main behavioral ambiguity.

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 no filler; the key operation and the preset-selection mechanism come first. The parenthetical '(fuzzy)' is slightly informal but is the only extra wording.

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?

For a destructive mutation with five undocumented parameters and non-obvious device targeting, the description is too thin. It has an output schema so return values need not be explained, but the input semantics and loss-of-state implications are missing.

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% across 5 parameters, so the description must carry the load, yet it only addresses 'preset' (fuzzy name or index). It leaves track_index, track_type, device_name and device_index completely unexplained, including how the two device selectors interact.

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?

States a specific verb and resource (switch a plug-in to a preset) and adds useful scope details: presets must be exposed, and selection works by fuzzy name or index. It is distinguishable from siblings like get_plugin_presets and load_plugin, but the description never names or contrasts those siblings.

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?

The description implies the tool is for changing presets but gives no when-to-use guidance: it doesn't say to call get_plugin_presets first to discover available presets, doesn't mention prerequisites (a loaded plugin that exposes presets), and offers no exclusions or alternatives.

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