Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Disconnect

tankg_disconnect

Releases control of the pedal so M-EFCS can be opened again. Use it to disconnect the USB connection and free the device after AI-driven preset or model operations.

Instructions

Release the pedal so M-EFCS can be opened again.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one real behavioral fact beyond the name: the call frees an exclusive hold on the pedal so another application can open it. It does not say whether in-flight settings are flushed, whether the tool errors when already disconnected, or what state the device is left in.

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 imperative sentence, front-loaded with the action, with no filler. It loses a point only because the one clause it does contain is framed around an undefined acronym rather than the tool's own resource.

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 no-parameter, no-output-schema tool the description is nearly adequate, but with zero annotations it should at least state the outcome of the call and whether it is safe to invoke when not connected. The unexplained 'M-EFCS' reference leaves an agent without the context needed to judge timing.

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 and the schema is an empty object, so there is nothing parameter-level for the description to explain. Baseline 4 applies; the sentence correctly implies no arguments are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Release' and object 'the pedal' convey a disconnect-like action, and the sibling 'tankg_connect' makes the pairing inferable. However, the description never actually says 'disconnect from the device' and leans on the unexplained acronym 'M-EFCS', so an agent must guess at the underlying operation.

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?

It gives an implied trigger: call this when you need to open M-EFCS again, i.e. when the pedal is being held exclusively. There is no explicit when-not-to-use guidance, no mention of the relationship to tankg_connect or tankg_status, and no statement of what happens if no connection exists.

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