Skip to main content
Glama
Sign In
Crystalize

Crystalize

by Peyton-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

eject

Stops a specified deck (1–4) and removes its disc at the end of the bar, freeing the deck for the next track.

Instructions

Stop a deck and take its disc off, at the end of the 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>"
    },
    "name": "eject"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYes1 to 4

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It says the deck is stopped and the disc removed, but not whether playback state is lost, whether the disc is returned in a response, whether this is reversible (versus drop_disc), or what permissions/guards apply. For a state-changing tool with zero annotation coverage this is thin.

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

Conciseness3/5

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

It is one short sentence, which is appropriately sized, and the action is front-loaded. However, the closing clause 'at the end of the bar' costs clarity rather than earning its place, since it introduces ambiguity without resolving any question.

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?

With no annotations and no output schema, the description is the only source of behavioral information, and it omits what happens to the ejected disc, what the call returns, and how it differs from the adjacent drop_disc/stop_mix tools. An agent could invoke it but could not predict the outcome.

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?

There is a single required parameter and schema coverage is 100%, with the schema itself stating the 1-4 range. The description adds nothing about the deck parameter, so the baseline 3 applies — the schema does all the work.

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

Purpose3/5

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

The verb phrase 'Stop a deck and take its disc off' does name an action and a resource, so an agent can form a rough idea. But the terminology is metaphorical ('deck', 'disc') and the trailing 'at the end of the bar' muddles whether this is a physical maneuver or a musical-phrase-timed operation. It never distinguishes itself from siblings like drop_disc or stop_mix.

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?

'at the end of the bar' is the only usage hint, and it is ambiguous (a musical bar? a UI bar?). No sibling is named, no when-not condition, and no prerequisites. The agent is left to guess whether eject or drop_disc is the right call.

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