Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Connect to the Tank-G

tankg_connect

Open the USB bridge to the M-VAVE Tank-G pedal so M-EFCS must be closed before connecting. Establishes the serial link needed to read, edit, and manage pedal presets.

Instructions

Open the USB bridge to the pedal. M-EFCS must be closed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tankg_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries full behavioral burden. It discloses one meaningful constraint (M-EFCS must be closed) but omits failure modes, whether the connection persists across calls, idempotency, or what a caller sees when the pedal is absent — notable gaps for a hardware-bridge tool.

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, prerequisite front-loaded immediately after the action, zero filler wording.

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 parameterless, annotation-free, output-schema-free tool, the description covers purpose and one prerequisite but leaves the interaction contract (ordering relative to other tools, error behavior) unstated. An agent could invoke it but could not confidently handle a failure.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty schema is consistent with the "just open the bridge" framing.

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?

"Open the USB bridge to the pedal" states a concrete verb and resource, and the sibling set contains a matching tankg_disconnect, so the connect/disconnect pairing is legible. It stops short of naming the sibling or stating that this must precede the other tankg_* operations.

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 prerequisite "M-EFCS must be closed" is a real usage condition, but the description never says when to call this versus tankg_status (which might report an existing connection) or what to do if already connected. Guidance 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.