Skip to main content
Glama
Sign In
Mooer Prime M2 MCP

Mooer Prime M2 MCP

by lucanenni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_drum_patterns

Read-onlyIdempotent

Retrieves drum pattern numbers and names so users can identify and choose patterns for playback or preset setup on the Mooer Prime M2 pedal.

Instructions

Names of the drum patterns (number → name).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare that this is a read-only, idempotent, non-destructive lookup. The description adds that the result is a number-to-name mapping, which is useful output context, but it does not describe completeness, ordering, or whether all drum patterns are returned.

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?

The description is a single compact sentence that front-loads the key information: it lists drum pattern names in a number-to-name format. There is no unnecessary wording.

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 simple, parameterless read-only lookup with annotations covering safety, the description is nearly complete. It could clarify whether all patterns are returned or what the number range represents, but it provides enough context to understand the output.

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 the baseline is 4. The description does not need to explain parameter meaning and appropriately focuses on the returned data.

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 clearly identifies the resource as drum pattern names and specifies the return shape as a number-to-name mapping. It does not explicitly differentiate from sibling tools such as set_drum, but the read-only listing purpose is evident.

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: call this tool when you need the mapping of drum pattern numbers to names. There is no explicit guidance about when to use it instead of alternatives like set_drum or list_presets, but the distinction is reasonably clear from the tool name and description.

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

Deploy Server

Other Tools