Skip to main content
Glama

Wait for something to happen

wait_for_event
Read-onlyIdempotent

Waits for live Minecraft events—player joins, deaths, chat, console lines, weather, and more—filtered by player or world, then returns the event or times out.

Instructions

Wait until an event happens live and get it, or time out. Types are WebSocket topics: player.join, player.leave, player.death, player.advancement, player.chat (chat:read), player.command and server.console (a console line; both logs:read), player.respawn, player.level_up, player.sleep, player.world_change, player.kill, player.craft, block.break, block.place, world.weather, world.night_skipped, entity.boss_killed, raid.start, raid.finish, server.status, and more. Narrow it to one player or world. Use it for “tell me when Steve logs in”, “wait until night is skipped”, or “wait for the console to say Done”. Keep timeoutSeconds within what your client lets a tool run.

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": {
      "types": "<types>"
    },
    "name": "wait_for_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesYesSuch as ["player.join"]
worldNoOnly this world's events
playerNoOnly this player's events
timeoutSecondsNoThen answers timedOut

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.1
    • addedInput schema / properties / timeoutSeconds / description
      Added value: +"Then answers timedOut"
  2. First observedv4.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: this is a blocking call, permission requirements are embedded per topic (chat:read, logs:read), and the client's own tool-timeout ceiling constrains timeoutSeconds. It does not describe the shape of the returned event payload, which matters since there is no output schema.

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?

Purpose and timeout semantics are front-loaded, and the topic list is dense but each entry is substantive given there is no enum in the schema. The closing note about client tool timeouts is a useful constraint rather than filler.

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 blocking, event-driven tool with no output schema, the definition covers what to ask for, how to narrow it, permission gates, and timeout behavior. The remaining gap is the return contract — what the retrieved event looks like and how 'timedOut' is surfaced — which the agent must infer.

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

Parameters5/5

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

Schema coverage is 100%, but the schema only offers 'Such as ["player.join"]' for types, with no enum. The description supplies the effective enumeration of WebSocket topics along with their permission implications, and explains that player/world are narrowing filters and that timeoutSeconds produces a timedOut answer.

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 opening sentence states a specific verb and resource ('wait until an event happens live and get it, or time out'), which is unambiguous. The word 'live' implicitly separates it from the sibling get_events (historical retrieval), but no sibling is named explicitly, so the differentiation is left to inference.

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

Usage Guidelines4/5

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

Three concrete usage examples ('tell me when Steve logs in', 'wait until night is skipped', 'wait for the console to say Done') make the intended context clear, plus narrowing guidance via player/world. It stops short of explicit exclusions — it never says 'for past events use get_events instead' or warn against using this for polling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.