Skip to main content
Glama
Sign In
Mooer Prime M2 MCP

Mooer Prime M2 MCP

by lucanenni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_loops

Read-onlyIdempotent

Lists all loop slots on the Mooer Prime M2, showing empty/recorded status, name, duration, and sync state so you can inspect looper contents before managing playback.

Instructions

The 10 loop slots: empty/recorded, name, duration, sync.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds that there are exactly 10 slots and what state each carries, which is useful behavioral context, but it says nothing about ordering, indexing, or how empty vs recorded is represented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Ten words with no filler, but it is a bare fragment rather than a front-loaded sentence stating the action. Brevity here reflects under-specification as much as efficiency.

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 zero-parameter read tool with full annotation coverage and no output schema, the description is the only source of return-value information, and it does enumerate the per-slot fields. However, it omits slot indexing/ordering and any indication of how to consume the result, leaving the agent to guess at the shape it will receive.

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 zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema itself has no properties to document.

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?

The description names the resource ('the 10 loop slots') and enumerates the per-slot attributes (empty/recorded, name, duration, sync), which goes slightly beyond the tool name. But it is a noun fragment with no verb, so it never explicitly says it lists or returns the slot state, and it draws no line against siblings like looper_control, set_looper, or export_loop.

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?

There is no when-to-use guidance at all: no mention of reading looper state before calling set_looper or looper_control, and no exclusions. The agent must infer that this is the read path for looper slots purely from the name.

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