Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Tweak active preset (unsaved)

tankg_set_live_values

Modify the active preset's live values, such as volume, gain, tone, and effects, without saving them to the preset.

Instructions

Change the active preset's live values without saving.

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": {
      "changes": "<changes>"
    },
    "name": "tankg_set_live_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses only that changes are not persisted; it says nothing about whether the live change is audible immediately, whether it can be reverted, what happens if no preset is active, or whether a device connection is required.

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 short sentence that is front-loaded with the action and ends on the most decision-relevant constraint ('without saving'). No wasted wording, though the extreme brevity leaves no room for the guidance the tool needs.

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 tool whose only input is a large nested configuration object with 0% schema description coverage, no output schema, and no annotations, one sentence is not enough. An agent cannot infer valid keys, merge semantics, or the operational preconditions from this definition.

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% at the parameter level and the single 'changes' object is deeply nested with many siblings (mod, delay, reverb, gain, cabSlot, color, etc.). The description adds no meaning about which keys are accepted, whether partial updates are allowed, or how nested objects merge with existing values.

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: changing the active preset's live values, with the qualifier 'without saving' that separates it from the persisting sibling tankg_update_preset. Sibling names are not cited explicitly, so it falls short of a 5.

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?

'Without saving' implies an ephemeral tweak scenario and implicitly contrasts with a save-oriented update, but it never states when to choose this over tankg_update_preset or tankg_select_preset, nor any prerequisites such as an active connection or selected preset.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.