Skip to main content
Glama
Sign In
Crystalize

Crystalize

by Peyton-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mute_deck

Mute or unmute a deck (1–4) without removing its disc, applying the change from the next bar.

Instructions

Mute or unmute a deck without taking its disc off, from the next bar.

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": {
      "deck": "<deck>",
      "mute": "<mute>"
    },
    "name": "mute_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYes1 to 4
muteYes

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?

With no annotations, the description carries the full burden. It does add real value by disclosing that the change is quantized to the next bar and that playback continues silently rather than stopping. It omits whether the state persists, how to read it back (get_state), and what happens on an empty deck or invalid deck number.

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 dense sentence with zero waste; the core action is front-loaded and the qualifiers (no disc removal, next-bar timing) sit immediately after it.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the essentials of the action and its timing but leaves error behavior, state persistence, and interaction with sibling transport tools unspecified.

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 50%: 'deck' is documented as 1–4 via min/max and a description, while 'mute' is an undocumented boolean. The description partially compensates by framing the parameter as mute-vs-unmute, implying true=mute and false=unmute, but adds no format or edge-case detail beyond that.

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 pair (mute/unmute) and a specific resource (deck), plus a clarifying effect: the disc keeps playing. It does not explicitly distinguish itself from the sibling solo_deck, which an agent could reasonably confuse with per-deck audio suppression.

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 only implied — 'from the next bar' signals a quantized, performance-safe toggle, which hints at live-mix contexts. It never states when to prefer this over solo_deck or stop_mix, and no preconditions (e.g. deck loaded) are given.

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