Skip to main content
Glama
Sign In
Crystalize

Crystalize

by Peyton-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

await_event

Waits for campaign-set events—requests, starts/ends, goal changes, crowd meter drops, or set end—returning new changes immediately or after a timeout; use between actions instead of polling.

Instructions

In a campaign set, wait until something happens and say what: a request coming, starting, ending within a few measures, passing or failing; a goal starting, done, or ending undone; the crowd meter coming on or falling below meter_below; the set ending; keep_alive stopping. Returns at once with anything since you last looked, else waits up to seconds, and gives get_set's view of the set with it. Call it between actions instead of polling get_set.

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

Input Schema

NameRequiredDescriptionDefault
secondsNoDefault 20, at most 60
meter_belowNoDefault 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool waits (blocking) up to `seconds`, returns immediately if events occurred since the last look, and returns get_set's view of the set. It does not cover timeout/empty-result handling or concurrency concerns, but the core behavior is well communicated.

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?

The description is front-loaded with the core purpose and packs necessary event details into a single paragraph. It is dense but avoids filler; a bulleted list of events might improve readability, but every sentence contributes relevant information.

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?

With no output schema and no annotations, the description still explains the return value ('gives get_set's view of the set') and the waiting semantics. It is complete enough for an agent to call the tool correctly, though it could mention what happens when `seconds` elapses with no events.

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%, so the schema already documents both parameters (defaults and max for `seconds`, default for `meter_below`). The description adds context for `meter_below` by tying it to 'crowd meter falling below' and for `seconds` as the wait bound, but this is minimal beyond what the schema already provides.

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+resource ('wait until something happens and say what' in a campaign set) and enumerates the event types it watches for. It also names the sibling it replaces ('instead of polling get_set'), so an agent can distinguish it from get_set without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it: 'Call it between actions instead of polling get_set.' It also explains the alternative behavior (returns at once with anything since last looked, else waits up to `seconds`), making the choice between this tool and get_set unambiguous.

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