Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Select preset

tankg_select_preset

Activates a preset on the Tank-G guitar pedal by slot name like "1A" or index 0-35, switching the pedal to that stored tone over USB.

Instructions

Make a preset active on the pedal.

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

Input Schema

NameRequiredDescriptionDefault
presetYesPreset as "1A".."9D" or index 0-35

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?

With no annotations, the description carries the full behavioral burden, yet it discloses almost nothing: it does not say whether the currently active preset is replaced, whether the change persists on the device or is session-only, whether a connection is required, or whether the operation can fail. Only the bare mutation semantics of 'make active' are conveyed.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, so nothing needs trimming. However, its brevity reflects under-specification rather than disciplined economy, leaving the reader with no more information than the title already provided.

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?

Considering the simple one-parameter mutation with full schema documentation and no output schema, the agent needs connection prerequisites, side effects on existing state, and persistence behavior to call this confidently. The description provides none of that, leaving a real gap for a hardware-mutating tool.

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

Parameters3/5

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

The single parameter has 100% schema description coverage documenting the '1A'..'9D' format and 0-35 index, so the schema already does the explanatory work. The description adds no additional meaning about accepted formats, valid ranges, or error behavior, which is the baseline expectation at full coverage.

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 ('make active') and resource ('preset') plus the target device ('the pedal'), which distinguishes it from siblings like tankg_get_preset, tankg_list_presets, and tankg_update_preset by implying state change on hardware. It stops short of explicitly naming which sibling it replaces, so it is clear but not fully differentiated.

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?

There is no when-to-use guidance, no mention of prerequisites such as an active connection (tankg_connect exists as a sibling), and no statement about when to prefer this over tankg_set_live_values or tankg_update_preset. The agent must infer all routing decisions.

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