Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Export presets

tankg_export_presets

Export all 36 pedal presets to an .atkg file for backup, transfer, or sharing in the M-EFCS preset format.

Instructions

Save all 36 presets to an .atkg file (same format as M-EFCS 'Share all presets').

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": {
      "path": "<path>"
    },
    "name": "tankg_export_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

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 carries the full behavioral burden. It discloses what is written (all 36 presets), the format (.atkg, M-EFCS 'Share all presets'), and the target (a file path), but says nothing about overwriting an existing file, whether a connected device is required (tankg_connect/tankg_disconnect are siblings), or what is returned on success.

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?

One tight sentence, front-loaded with the action and scope; the parenthetical format reference earns its place by orienting users familiar with M-EFCS. Nothing is wasted, though 'M-EFCS' is unexplained jargon.

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 one-parameter export tool with no output schema or annotations, the description covers intent and format but leaves the operational essentials — connection prerequisite, overwrite semantics, confirmation of what the file contains — unstated.

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 coverage is 0% — 'path' is an undescribed string. The description partially compensates by revealing that path is a destination .atkg file, but does not clarify absolute vs relative paths, overwrite behavior, or whether a directory is acceptable.

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 and resource — save all 36 presets — and names the destination artifact type (.atkg file), which distinguishes it from tankg_import_presets and tankg_read_preset_file. It does not explicitly name a sibling it replaces, so it stops short of full differentiation.

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 word 'all' implies this is the bulk/full-backup path, but the description never states when to choose this over tankg_read_preset_file, tankg_list_presets, or tankg_import_presets. No prerequisites or exclusions are given.

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