Mooer Prime M2 MCP

Overview Schema Source Related Servers Discussions Admin

backup_all_presets

Read-onlyIdempotent

Exports all 80 presets to one bank JSON file over USB, providing a complete backup before editing or restoring pedal settings.

Instructions

Export all 80 presets to one bank JSON file (USB, takes a while).

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": "backup_all_presets"
  }
}

Input Schema

Name	Required	Description	Default
`file`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare this is a safe, idempotent, non-destructive read, so the description's job is to add operational context — which it does by disclosing the destination (USB) and the latency warning ("takes a while"). It does not say where on USB the file lands or whether an existing file is overwritten, which are the remaining meaningful gaps.

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?

A single front-loaded sentence carrying scope, output format, destination, and cost with no filler. Nothing in it is redundant.

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 one-parameter export tool with a full annotation set and no output schema, the description covers scope, destination, and duration adequately. The undocumented file parameter is the notable omission that keeps it from being complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter "file" has zero schema description coverage, and the description never mentions it — an agent cannot tell from the definition whether it is a path, a filename, or optional. Because coverage is 0%, the description needed to compensate here and does not.

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 names a specific verb and resource ("Export all 80 presets") plus the output artifact ("one bank JSON file"), which implicitly separates it from the singular sibling backup_preset. It stops short of naming that sibling explicitly, so the differentiation is inferable rather than stated.

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?

"Export all 80 presets" implies the bulk/whole-bank use case versus the per-preset backup_preset, and "takes a while" signals a cost worth weighing. There is no explicit when-to-use or when-not-to-use statement and no mention of restore_preset as the counterpart operation.

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