Skip to main content
Glama
Sign In
Mooer Prime M2 MCP

Mooer Prime M2 MCP

by lucanenni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_sample

Destructive

Deletes a sample slot's USB file after exporting it to backups, so users can remove sample files while preserving a backup copy.

Instructions

Delete a sample slot's file (USB). The file is exported to backups first.

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": {
      "kind": "<kind>",
      "slot": "<slot>",
      "confirm": "<confirm>"
    },
    "name": "delete_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
slotYes
confirmYesMust be true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered upstream. The description does add genuinely valuable context beyond that: the file is exported to backups before deletion, which softens the perceived risk. It still omits whether the slot becomes empty/unusable afterward, where backups live, and whether the operation can fail.

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

Conciseness4/5

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

Two short sentences, front-loaded with the action and target. The backup sentence is slightly cryptic (backups of what, where) but earns its place as risk information.

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

Completeness2/5

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

For a destructive, non-idempotent mutation with no output schema, the description should say what the agent gets back and what state the slot ends in. It covers the backup safety net but leaves the post-delete state and error behavior unaddressed.

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?

Schema coverage is only 33%, but the description compensates by framing the target as a slot file, which explains why 'slot' (1-10) is required. The 'kind' enum values (drive/pre-amp/entire-amp/cab) and the 'confirm' boolean are left unexplored, but the confirm schema description already states 'Must be true'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (delete) plus a precisely identified resource (a sample slot's file), with the storage medium (USB) named. It is clearly distinguishable from siblings like export_sample, import_sample, and list_samples.

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?

No guidance on when to use this vs export_sample (which also handles sample files) or how to know which slot to target. The only hint is the note that files are backed up first, which is not usage routing.

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