Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Import presets

tankg_import_presets

Replaces all 36 Tank-G presets with an .atkg file while saving a backup of the current presets first.

Instructions

Replace all 36 presets with an .atkg file. A backup of the current presets is saved first.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose the two facts an agent most needs: every one of the 36 presets is destroyed, and a backup is taken first. It stops short of stating that a device connection is presumably required or what happens on an invalid/corrupt .atkg file, which a zero-annotation destructive tool ideally would cover.

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 waste, and the destructive scope is front-loaded with the safety mitigation second — exactly the right ordering for a replace-everything operation.

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

Completeness4/5

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

For a one-parameter destructive tool with no annotations and no output schema, the description covers scope and recoverability, which are the critical unknowns. Only prerequisites (connect state, file validity, failure behavior) are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the single 'path' parameter is undocumented in the schema. The description compensates meaningfully by tying that path to an .atkg file, telling the agent the expected format and that it points at a file rather than an ID or name.

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?

The description uses a specific verb and resource — 'Replace all 36 presets' — and pins down the file type (.atkg). That makes it immediately distinguishable from tankg_export_presets, tankg_list_presets and tankg_read_preset_file without opening any schema.

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 all-or-nothing replacement semantics imply the use case (restoring a preset bank from a file), so an agent can infer when this is appropriate. But it names no alternatives and gives no explicit 'do not use when you only want to inspect or read a file' guidance, leaving routing to inference.

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