Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Update preset

tankg_update_preset

Updates stored Tank-G preset values, optionally saving to pedal flash with automatic backup and applying changes live when the preset is active.

Instructions

Change values of a stored preset. With save=true (default) it is written to the pedal's flash (a backup of all presets is taken first). If the preset is active, the change is also applied live.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "preset": "<preset>",
      "changes": "<changes>"
    },
    "name": "tankg_update_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNo
presetYesPreset as "1A".."9D" or index 0-35
changesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the flash-write default (save=true), that a backup of all presets occurs first, and that active presets receive the change live. It stops short of stating connection requirements, whether unspecified fields are preserved or reset, and error behavior.

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?

Three short sentences, no filler, and the core action plus the persistence semantics are front-loaded. Every clause carries information an agent would otherwise have to guess.

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 mutation tool with no annotations, no output schema, and a deep nested `changes` schema, the description covers the critical persistence behavior but leaves gaps: prerequisites, merge-vs-replace semantics for partial `changes`, and what the call returns. Adequate but not complete.

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 only 33% and the nested `changes` object has thirteen sub-properties, almost none documented in the description. The description does add genuine value for `save` (its default and its flash/backup side effect), but it says nothing about `preset` addressing or the semantics of `changes` fields.

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?

States a specific verb and resource: "Change values of a stored preset." The word "stored" scopes it to persisted presets, which implicitly separates it from a live-values tool, but no sibling is named or explicitly excluded.

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 rather than stated: the save=true explanation tells the agent this writes to flash, and the live-application sentence tells it an active preset is affected. There is no guidance on when to prefer this over tankg_set_live_values-style changes, nor any stated prerequisite such as an active connection.

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