Skip to main content
Glama
Sign In
Crystalize

Crystalize

by Peyton-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

take_snapshot

Saves the current mix to the player's profile as a snapshot on the next downbeat, so goals requiring a snapshot can be completed.

Instructions

Save the mix playing as a snapshot, as FUSER's Take Snapshot key does, on the next downbeat, for goals that ask for one. Each is kept in the player's profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "take_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations, so the description carries the burden. It usefully discloses two behaviors: the capture is deferred to the next downbeat, and the result persists in the player's profile. It does not say whether the call blocks until the downbeat, whether repeated calls overwrite prior snapshots, or what a failure (e.g., nothing playing) looks like.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. The game-reference aside is slightly decorative but reinforces the semantics of 'snapshot' versus a saved mix.

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 zero-param, no-output-schema action the description covers the essentials, but the timing behavior creates a real open question — does the call return immediately or only at the downbeat? — that an agent needs answered to sequence subsequent tools correctly.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to clarify beyond the implicit target of 'the mix playing'. Baseline 4 applies for a zero-parameter tool.

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?

The description states a concrete verb+resource (save the currently playing mix as a snapshot) and anchors it to a familiar game action and its timing. However, it never distinguishes this from the sibling save_mix, so an agent still has to infer which persistence concept applies.

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?

'for goals that ask for one' gives a loose trigger condition, but there is no explicit when-not or comparison to save_mix/plan_mix. Usage is implied rather than specified.

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