Skip to main content
Glama
Sign In
Crystalize

Crystalize

by Peyton-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_set

Retrieve the current campaign set's state—active measures, crowd requests, goal progress, crowd meter and warnings, mix freshness, and score—to plan your next DJ move in FUSER.

Instructions

In a campaign set: the measure FUSER is on, the open crowd requests with what each wants and the measure it ends on, the goals not yet done with their progress, how many of each are settled, whether the section has a crowd meter, the meter from 0 to 100 and its band (low, medium, high, peak) and warnings, the mix's freshness from 0 to 100, which a new drop raises and a still stretch lets fade, and the score. Measures are FUSER's own, not a mix's bars. A goal's text may keep a placeholder such as {Transition} the mod cannot read yet.

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": "get_set"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 discloses returned domains and some dynamics (freshness rises with a new drop, fades on a still stretch; meter bands and warnings; placeholder text may remain), but it omits operational behavior such as error conditions or whether a campaign must be active.

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?

The description is a single dense run-on fragment with many clauses. It is information-rich and not repetitive, but the front-loading is weak and the structure makes it hard to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter getter with no output schema, the description must explain return content. It enumerates nearly all returned components and includes notable caveats (FUSER-owned measures, unread placeholders), though it leaves out state prerequisites and output format details.

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 zero parameters, so the baseline is 4. No parameter semantics are needed, and the description does not introduce any parameter confusion.

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 enumerates the campaign-set data returned (measure, requests, goals, crowd meter, freshness, score), making the resource clear. It lacks an explicit verb like 'returns' and does not distinguish the tool from sibling get_state.

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?

There is no guidance on when to call this tool versus alternatives such as get_state, nor any stated preconditions like being in campaign mode. Usage must be inferred entirely from the field list.

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