Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Install a TONE3000 model on the Tank-G

tankg_install_tone3000_model

Download a TONE3000 model and install it to a Tank-G amp or cab slot; omit the slot to preview only, and note that installing overwrites existing slot content.

Instructions

Download a TONE3000 model and send it to the pedal: .nam (A2) goes to amp slot 1-9, .wav IR goes to cab slot 1-8. Without slot it is only previewed. Overwrites the slot.

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": {
      "modelId": "<modelId>"
    },
    "name": "tankg_install_tone3000_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
slotNo
modelIdYes
cabLevelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing the destructive trait ('Overwrites the slot') and the preview-vs-write distinction, which an agent could not otherwise know. It does not cover required credentials/connection state, behavior on invalid slot-for-file-type mismatch, or what a preview actually does, which is a notable gap for an unannotated mutating tool.

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?

Three short sentences, front-loaded with the action and destination, then the routing rules, then the destructive warning. Almost no wasted wording, though the colon-heavy packing of file-type-to-slot rules reads slightly telegraphically.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a 4-parameter compound install tool with no annotations and no output schema, the description covers the essential decision points: destination routing by file type, the preview default when slot is omitted, and the overwrite side effect. Remaining gaps (name/cabLevel meaning, auth prerequisites) are what keep individual dimension scores down rather than rendering the definition unusable.

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 0%, so the description must carry all parameter meaning. It handles slot well (1-9 for .nam/A2, 1-8 for .wav IR, omission = preview), but 'name' and 'cabLevel' are entirely unexplained, and modelId is only implied by 'a TONE3000 model'. Two of four parameters remain opaque.

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 concrete two-step action (download a TONE3000 model, send it to the pedal) and names the destination resource (amp slot / cab slot). This implicitly separates it from tone3000_download_model (download only) and from tankg_upload_amp_capture/tankg_upload_cab_ir (local file upload), but it never names those siblings explicitly, so the differentiation is inferred rather than stated.

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 slot it is only previewed' gives a clear behavioral fork for the slot parameter and effectively says when the tool writes vs. previews. However, there is no guidance on prerequisites (TONE3000 auth, pedal connected) or on when to prefer this over the download-only or local-upload siblings, leaving the agent to infer the boundaries.

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