Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Upload amp capture

tankg_upload_amp_capture

Convert a TONE3000/NAM A2 capture (.nam) to A2 Lite (Original), then send it to a Tank-G pedal: use slot 1-9 to overwrite an amp slot or omit slot for preview only.

Instructions

Convert a TONE3000/NAM A2 capture (.nam) to 'A2 Lite (Original)' and send it to the pedal. With slot 1-9 it overwrites that amp slot; without slot it is only previewed (not stored).

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": {
      "namPath": "<namPath>"
    },
    "name": "tankg_upload_amp_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
slotNo
namPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 disclose the critical behavioral trait — that providing a slot causes a destructive overwrite while omitting it is a non-persistent preview — which is valuable. However it says nothing about prerequisites (pedal connection/session), whether an overwrite is reversible, or what the preview mode returns.

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 short sentences, zero filler. The core action is front-loaded and the slot/no-slot distinction follows immediately, which is exactly the order an agent needs to decide how to call it.

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 definition covers the highest-risk aspect (overwrite vs preview) well. But it omits the connection prerequisite, the role of the name parameter, and any description of what the preview step yields, leaving meaningful gaps for a state-changing 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?

Schema description coverage is 0%, so the description must compensate. It gives meaning to namPath (the source .nam capture) and slot (1-9, overwrite semantics), but the third parameter, name, is not mentioned at all — its 13-character constraint and effect on the stored capture are left entirely to the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb chain ('Convert ... and send it to the pedal') plus the exact resource (a TONE3000/NAM A2 .nam capture) and the transformation applied ('A2 Lite (Original)'). The resource and file format make it clearly distinguishable from the sibling tankg_upload_cab_ir without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes the two operating modes and their consequences: with slot 1-9 it overwrites that amp slot, without slot it is only previewed and not stored. That is real when-to-use guidance. It lacks any named alternative or exclusion (e.g. when to use tankg_install_tone3000_model or how to obtain the .nam first).

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