Skip to main content
Glama

wait_for_message

Read-only

Blocks until a new QQ message arrives, optionally filtered by chat, sender, or text, up to a timeout. Use it to wait for a reply before continuing.

Instructions

Block until a new message arrives (optionally only from a chat / sender / containing text), up to timeout_seconds. Good for "reply when they answer" flows.

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

Input Schema

NameRequiredDescriptionDefault
targetNoOnly this chat
containsNoOnly messages containing this text
from_userNoOnly from this QQ number
include_selfNoAlso match my own messages
timeout_secondsNoMax wait (≤ 600)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already establish read-only, non-destructive, open-world behavior. The description adds the important blocking behavior and timeout ceiling context, but it does not disclose what happens when the timeout expires, such as whether it returns empty, raises an error, or consumes matching messages.

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?

The definition is two sentences and front-loads the core behavior. Every phrase contributes useful information: blocking, optional filters, timeout, and a concrete use case.

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 waiting tool with annotations and full schema coverage, the definition covers the main interaction. However, with no output schema, it should ideally state what is returned on timeout or how the received message is represented, which is a meaningful completeness gap.

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 all five parameters are already documented in the schema. The description restates the main filters and timeout but adds little semantic detail beyond the schema, making the baseline score appropriate.

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 specific verb and resource: blocking until a new message arrives, with optional filters. It is clear what the tool does, but it does not explicitly contrast itself with the sibling wait_for_event tool, leaving a small gap in sibling differentiation.

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?

It gives a concrete usage scenario, "Good for 'reply when they answer' flows," which helps an agent decide when to use it. It does not name alternatives or state when not to use this tool, so it falls short of full when/when-not guidance.

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