Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Read .atkg file

tankg_read_preset_file

Decode an .atkg preset file offline to inspect its settings without connecting a pedal. Use it to read and verify Tank-G preset contents from disk.

Instructions

Decode an .atkg preset file offline (no pedal needed).

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_read_preset_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two useful traits: the operation is a pure decode (non-mutating) and requires no hardware connection. It omits what happens on a malformed/non-.atkg file, whether the path is local to the server filesystem, and what the decode yields.

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?

One short sentence with the key differentiator front-loaded in parentheses; every word earns its place and nothing is padded.

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 simple one-parameter read tool this is close to adequate, but with no output schema the description should indicate what a decoded preset looks like (raw JSON/structure) and whether failures are surfaced. Those gaps are the main thing an agent would still need.

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%, and the single 'path' parameter is documented only as a string. The description compensates partially by identifying the target as an .atkg preset file, but says nothing about absolute vs relative paths, filesystem locality, or encoding.

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?

Specific verb 'Decode' plus specific resource '.atkg preset file', and the parenthetical 'no pedal needed' implicitly separates it from the connected sibling tankg_get_preset. It stops short of naming that alternative, so an agent must infer the pairing.

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?

'(no pedal needed)' implies the operating condition — use this when working offline without a connected device — but there is no explicit when-not guidance and no named alternative to route between. Usage is implied rather than stated.

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