Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Download from TONE3000

tone3000_download_model

Downloads a NAM model (.nam) or cabinet IR (.wav) from TONE3000 by model ID, enabling AI assistants to install it on an M-VAVE Tank-G pedal.

Instructions

Download one model (.nam) or IR (.wav) by model id.

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": "tone3000_download_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNo
modelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says 'Download' but never states where the file lands, whether an existing file is overwritten, whether authentication is required, or whether the file is saved to disk versus returned inline — all critical for a filesystem-writing operation.

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 front-loaded sentence with no filler; the file extensions are a useful touch. It is efficient, though the terseness comes at the cost of the missing guidance noted elsewhere.

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?

With no annotations, no output schema, and zero schema description coverage on two parameters, the description should explain the destination directory, the return value (e.g. saved path), and any auth requirement. None of that is present, so an agent cannot call this correctly without guessing about 'dir'.

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%, so the description must compensate. It clarifies modelId as the model identifier and implies the file type is derived from the model, but the 'dir' parameter is never mentioned at all — no default, no format, no statement about whether it must exist.

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 (Download) and resource (one model .nam or IR .wav) keyed by model id, which is concrete enough for an agent to distinguish it from siblings like tankg_install_tone3000_model or tone3000_search. It stops short of explicitly contrasting itself with those siblings, so it lands at 4 rather than 5.

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 (e.g. needing a model id from tone3000_search, or being authenticated via tone3000_auth_status/tone3000_login_finish), and no statement about when to prefer this over tankg_install_tone3000_model. The phrase 'by model id' hints at an input requirement but gives no routing logic.

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