Skip to main content
Glama

wait_for_event

Read-only

Blocks until a specified QQ event type arrives, such as a friend request or group increase, with a configurable timeout; use it to wait for live account activity before responding.

Instructions

Block until an event of the given types arrives (e.g. "notice.group_increase", "request.friend", "notice.group_recall").

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
typesYespost_type or post_type.subtype values
timeout_secondsNoMax wait (≤ 600)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds the useful behavioral fact that the call blocks until an event arrives, but it does not explain timeout behavior, what happens if no event arrives, or what is returned.

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?

It is a single, front-loaded sentence with no filler. The blocking behavior and examples are presented immediately and efficiently.

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 simple two-parameter read-only wait tool, the description plus schema is enough to invoke it. However, with no output schema, it does not describe what the tool returns or how timeout expiry is represented, which leaves a meaningful gap for interpreting results.

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?

Schema description coverage is 100%, so parameter documentation is already strong. The description adds value by showing concrete examples such as 'notice.group_increase' and 'request.friend' for the types parameter, clarifying the expected string format beyond the schema's 'post_type or post_type.subtype values'.

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 uses a specific verb and resource: 'Block until an event of the given types arrives,' and gives concrete examples of event type strings. It does not differentiate from the sibling wait_for_message, so it stops short of the top score.

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?

The description implies usage through the blocking wait semantics and examples, but it does not state when to prefer this tool over wait_for_message or other alternatives. No exclusions or prerequisites are given.

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