Skip to main content
Glama
Sign In
easyeffects-mcp

easyeffects-mcp

by kaushikgunasekaren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_plugin_property

Set one property on an active Easy Effects plugin, such as input gain or bypass, and return the value read back.

Instructions

Set one property of an active plugin. Returns the value read back from Easy Effects.

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": {
      "pipeline": "<pipeline>",
      "plugin": "<plugin>",
      "property": "<property>",
      "value": "<value>"
    },
    "name": "set_plugin_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
pluginYesPlugin name, e.g. equalizer, compressor, limiter
channelNoEqualizer only
instanceNo
pipelineYes
propertyYesProperty name in camelCase, e.g. inputGain, bypass

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does usefully disclose a read-back verification behavior and that the plugin must be 'active', but omits persistence, permissions, side effects, and error behavior for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core action and return behavior front-loaded; no filler or redundancy.

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?

An output schema exists, so return values need not be explained, and the description wisely notes the read-back. However, for a six-parameter mutation tool with no annotations, it lacks prerequisites and behavioral detail an agent would need to invoke it safely.

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 coverage is only 50% (value, instance, and pipeline are undocumented) and the description compensates with nothing beyond 'one property'. It adds no meaning over the schema for the undocumented parameters.

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 (Set) and resource (one property of an active plugin), and clarifies scope with 'one property' and 'active plugin'. It implicitly distinguishes itself from get_plugin_property and set_equalizer_band, though it never names a sibling explicitly.

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?

Contains no when-to-use guidance, prerequisites, or alternative routing. With siblings like set_equalizer_band and apply_parametric_eq, an agent gets no signal on which setter to pick or when this is preferred.

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