Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Get preset

tankg_get_preset

Read a stored preset or the active preset's live unsaved values from the Tank-G pedal to inspect settings before editing, saving, or switching.

Instructions

Read one stored preset, or the live (unsaved) values of the active one.

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

Input Schema

NameRequiredDescriptionDefault
liveNo
presetNoPreset as "1A".."9D" or index 0-35

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies a non-mutating operation and the parenthetical clarifies that live values are unsaved, but nothing is said about errors for missing/invalid presets, permission or connection prerequisites, or that no state is changed.

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 front-loaded sentence with no filler, and the two-mode distinction is placed early. It is tight, though slightly elliptical in the phrase 'the active one'.

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

Completeness2/5

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

There is no output schema, so the description would need to indicate what a returned preset contains, and it does not. For a two-parameter read with optional parameters and one undocumented flag, the definition leaves too much to inference.

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 50%: the preset format ('1A'..'9D' or index 0-35) is documented in the schema, while the live boolean is not. The description partially compensates by explaining that live means unsaved values of the active preset, but it does not say what happens when live is false and preset is omitted.

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?

The description gives a specific verb and resource ('Read one stored preset') and adds a second distinct mode ('or the live (unsaved) values of the active one'), so the agent can tell what is being fetched. It does not disambiguate against siblings such as tankg_list_presets or tankg_read_preset_file, which keeps it below a 5.

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?

Usage is implied by the two modes: fetch a stored preset, or fetch live unsaved values of the active preset. However, there is no explicit when-to-use guidance versus listing presets or reading a preset file, and no statement that both parameters are optional or what happens when neither is supplied.

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