Mooer Prime M2 MCP

Overview Schema Source Related Servers Discussions Admin

list_presets

Read-onlyIdempotent

Retrieve all 80 Mooer Prime M2 presets with bank labels and names, optionally including each preset's effect chain for chain-aware setup or editing.

Instructions

List the 80 presets (number, bank label such as 0A, name). With with_chains, also each preset's effect chain.

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

Input Schema

Name	Required	Description	Default
`with_chains`	No	Include effect chains (waits for the background scan, a few seconds)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this a safe, read-only, idempotent operation, so the bar is lower. The description adds genuine context by fixing the result size at 80 presets and disclosing that chains are an optional extra payload, which tells the agent the default response is a bounded enumeration.

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?

Two short sentences, with the scope and default shape front-loaded before the optional expansion. Every clause carries information; nothing is padded or repeated.

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

Completeness4/5

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

For a single-optional-flag list tool with no output schema, the description covers what is returned and how the flag changes it. The only gap is that the scan-wait for with_chains lives solely in the schema rather than the description, a minor omission given full schema coverage.

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 100%, so the boolean with_chains is already documented in detail, including the scan-wait behavior. The description restates its effect at a high level without adding format or cost detail beyond the schema, so the baseline of 3 applies.

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 states a concrete verb and resource ('List the 80 presets') and even enumerates the returned fields (number, bank label such as 0A, name), which cleanly separates it from the singular get_preset sibling. It stops short of naming that sibling explicitly, so the differentiation is implicit 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?

The description implies the context (browsing the preset bank) and explains the with_chains option extends the payload. It gives no explicit guidance on when to prefer this over get_preset or select_preset, and offers no exclusions or prerequisites.

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