Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Pedal status

tankg_status

Retrieves the active preset and bypass state from the Tank-G pedal, so you can check which tone is loaded and whether the effect is engaged.

Instructions

Active preset and bypass state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden, and it says nothing about whether the device must be connected, whether the call is free of side effects, or what happens if no preset is loaded. 'State' weakly implies read-only, but nothing is confirmed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short phrase with no waste, but it is a noun fragment rather than a front-loaded sentence, and its brevity reflects under-specification rather than disciplined editing.

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 zero-parameter read tool with no output schema, the description should at least characterize the returned values; 'active preset and bypass state' hints at the fields but gives no shape (preset name vs. index, boolean vs. enum). It is minimally adequate but thin given there is no output schema to fall back on.

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 baseline for a no-arg tool applies. No misleading parameter language is present.

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 fragment 'Active preset and bypass state' identifies the two pieces of state the tool reports, which goes slightly beyond the name/title. However, it lacks a verb (read/get/report) and does not distinguish itself from siblings like tankg_get_preset or tankg_set_bypass, leaving the agent to infer that this is a read-only status query.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus tankg_get_preset, tankg_list_presets, or the setter tools; nor is any precondition such as 'after tankg_connect' mentioned. Usage is only implied by the word 'state'.

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