Skip to main content
Glama
Sign In
Crystalize

Crystalize

by Peyton-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_key

Changes the DJ session's musical key from the next bar so all decks stay in sync; pass a key like Ab or Abm.

Instructions

Change the session's key from the next bar. Every deck follows.

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": {
      "key": "<key>"
    },
    "name": "set_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesAb for A flat major, Abm for minor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 behavioral burden. It usefully discloses timing ('from the next bar') and global scope ('Every deck follows'), but does not state whether the change is reversible, whether currently playing tracks are transposed or key-locked, or what happens on invalid key input.

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?

Two compact sentences with the effect timing and scope front-loaded. Nothing is repeated or wasted.

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?

Adequate for a single-parameter setter, but with no annotations and no output schema the description should do more. It leaves undefined what 'follows' means operationally for live playback and whether any confirmation or error state is returned.

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 description coverage is 100%, and the schema already explains the notation ('Ab for A flat major, Abm for minor'). The tool description adds no further parameter semantics beyond the word 'key', so baseline 3 is appropriate.

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?

States a specific verb and resource: 'Change the session's key'. 'Every deck follows' makes the global harmonic scope explicit and distinguishes it from per-deck operations like mute_deck or solo_deck.

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?

Implies that this is used to set the harmonic key globally for all decks, but gives no explicit when-to-use/when-not guidance and names no alternatives. For a session-level setter among many deck-specific tools, a sentence like 'use before playback or while mixing; does not affect individual deck keys unless set' would close the gap.

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