Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Upload cab IR

tankg_upload_cab_ir

Upload a WAV cab impulse response to the M-VAVE Tank-G pedal; use slot 1–8 to overwrite a cab slot, or omit slot to preview the resampled IR.

Instructions

Send a WAV impulse response to the pedal (resampled to 44.1 kHz, max ~30 ms). With slot 1-8 it overwrites that cab slot; without slot it is only previewed.

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": {
      "wavPath": "<wavPath>"
    },
    "name": "tankg_upload_cab_ir"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotNo
levelNo
wavPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well: it reveals automatic resampling to 44.1 kHz, a ~30 ms length ceiling, that a slot write is destructive ('overwrites that cab slot'), and that a slotless call is non-persistent preview. It leaves out whether an existing IR is recoverable after overwrite and whether a connected session 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.

Conciseness5/5

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

Two dense sentences, with the format constraints folded into a parenthetical and the consequential slot/no-slot behavior placed last where it drives the decision. No filler or restatement of the tool name.

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?

For a mutation tool with no annotations and no output schema, the description covers the format, size limit, and destructive/preview branching but omits the 'level' parameter's effect and any precondition about the pedal being connected. An agent could call it but would be guessing at one parameter and at session requirements.

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?

Schema description coverage is 0%, so the description must compensate for all three parameters. It explains 'slot' thoroughly (range 1-8, overwrite vs preview), but says nothing about 'level' (0-100) and only implicitly covers 'wavPath' via the format constraints, leaving one parameter's meaning entirely undefined.

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?

'Send a WAV impulse response to the pedal' states a specific verb and resource, and the parenthetical narrows it to a cab IR (44.1 kHz, ~30 ms). It is clearly distinct from tankg_upload_amp_capture by resource type, though the description never names that sibling to make the split explicit.

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?

The slot/no-slot conditional ('With slot 1-8 it overwrites that cab slot; without slot it is only previewed') gives real guidance on the two usage modes and implies the persist-vs-audition decision. It stops short of stating prerequisites (e.g. that a connection must already be established) or naming any alternative tool for comparison.

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