Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Effect types

tankg_effect_types

Resolve effect type indexes and names for Tank-G pedal knob zones, mapping 0 (first) and 2 (last) to the correct effect type.

Instructions

Effect type indexes and names (0 = first knob zone, 2 = last).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden. It does disclose the semantic meaning of the index range (first knob zone to last), which is genuine behavioral context, but it never states that this is a read-only, zero-argument lookup or what shape the returned index/name pairs take.

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 short sentence with the resource front-loaded and no filler. The parenthetical is terse to the point of being cryptic, but nothing is wasted.

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 trivial zero-param tool the description is nearly adequate, but with no output schema the agent still has no clear picture of the return value (a list of {index, name} pairs?) or how many effect types exist. The index-range hint partially compensates but leaves gaps.

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 no parameters, so there is no parameter semantics to explain; the baseline for a zero-param tool applies. The description does not confuse the reader with nonexistent inputs.

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?

"Effect type indexes and names" identifies the resource being retrieved, but there is no verb (list/get/lookup) and no statement that this is a reference lookup rather than a mutation. The parenthetical "0 = first knob zone, 2 = last" is domain jargon that only partly clarifies what the returned indexes mean.

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?

No when-to-use guidance at all: nothing says to call this before setting effect values, nor how it relates to sibling tools like tankg_set_live_values or the preset tools. The agent must infer the lookup role from the name alone.

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