Skip to main content
Glama
Sign In
Mooer Prime M2 MCP

Mooer Prime M2 MCP

by lucanenni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_effect

Destructive

Remove an effect from a specified pedal slot and move later effects up to maintain effect-chain order.

Instructions

Remove the effect in a slot; later effects move up.

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": {
      "slot": "<slot>"
    },
    "name": "remove_effect"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYesPosition in the chain, 1 = first

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?

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds a genuinely non-obvious consequence beyond them: 'later effects move up,' i.e. the chain reindexes after removal. It doesn't address undoability or whether removal is immediate, which keeps it from a 5.

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?

A single front-loaded sentence where both clauses earn their place: the action first, then the side effect. No filler or redundancy.

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 one-parameter tool with rich annotations, the description covers the action and the key post-removal behavior. Minor gaps (permanence, undo, confirmation needs) are acceptable given destructiveHint is already set.

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% and the slot parameter is fully documented ('Position in the chain, 1 = first'). The description's phrase 'in a slot' is consistent but adds no syntax or constraint information beyond the schema, so baseline 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?

States a specific verb and resource: 'Remove the effect in a slot,' which cleanly separates it from add_effect, move_effect, and edit_effect among the siblings. It doesn't explicitly name a sibling to contrast with, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance and does not point to alternatives such as edit_effect for disabling rather than deleting. Usage is only implied by the verb.

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