Skip to main content
Glama
Sign In
Mooer Prime M2 MCP

Mooer Prime M2 MCP

by lucanenni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

copy_preset

Destructive

Copies one stored preset slot onto another USB slot, backs up the target's previous content, and verifies the write.

Instructions

Copy the stored version of one preset slot onto another (USB). The target's previous content is backed up and the write is verified.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "copy_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description adds important behavior: the target's previous content is backed up and the write is verified. It does not explain backup accessibility or failure semantics, but it meaningfully clarifies the destructive operation.

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 two efficient sentences, front-loads the core copy operation, and adds only high-value behavioral context about backup and verification.

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 two-parameter destructive copy with annotations and no output schema, the description covers the key operation, target backup, and write verification. Minor gaps remain around slot indexing and backup details, but the definition is largely 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?

With 0% schema description coverage, the description partially compensates by clarifying that the integer parameters refer to preset slots and that the operation copies a stored version from one to another. It does not explicitly map 'from' and 'to' or mention the 1-80 slot range.

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 specific verb and resource: copying the stored version of one preset slot onto another. It is clear what the tool does, though it does not explicitly name sibling alternatives such as backup_preset or save_preset.

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?

The description gives no guidance on when to use this tool versus alternatives like backup_preset, restore_preset, or save_preset. It implies a slot-to-slot copy but provides no exclusions or selection conditions.

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