Skip to main content
Glama
Sign In
Crystalize

Crystalize

by Peyton-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

solo_deck

Toggles solo state for a selected FUSER deck (1–4) starting at the next bar, enabling an agent to isolate or restore that deck during a DJ mix.

Instructions

Solo or unsolo a deck, 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>",
      "solo": "<solo>"
    },
    "name": "solo_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYes1 to 4
soloYes

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?

With no annotations, the description carries the full burden. It usefully discloses that the change applies from the next bar, but it does not say what solo does to other decks (e.g., mutes them), whether it is a toggle, or what state changes occur on unsolo.

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 with zero fluff; the timing detail is placed immediately after the action.

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 state-changing mixer control with no annotations and no output schema, the description omits key information: the effect on other decks, the boolean semantics, and when to use it. It is too terse to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: deck is described as '1 to 4' and solo has no schema description. The description does not clarify that solo=true enables solo and solo=false disables it, nor does it add any meaning beyond the bare parameter names.

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+resource ('solo or unsolo a deck') and adds timing ('from the next bar'). It is distinct from mute_deck, though it does not explicitly name that sibling or clarify the difference.

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 versus mute_deck or other mixer tools, nor when to avoid it. The timing note is behavioral, not usage context.

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