Skip to main content
Glama

reply_to_message

Quote-reply to a QQ message by message_id in group or private chats, optionally mentioning the original sender.

Instructions

Quote-reply to a message by its message_id (works for group and private messages). Optionally @ the original sender.

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": {
      "message_id": "<message_id>",
      "text": "<text>"
    },
    "name": "reply_to_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesReply text (inline tokens like send_text)
message_idYesmessage_id to reply to
mention_senderNoAlso @ the sender (groups)

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?

The annotations already disclose that this is a non-read-only, non-destructive, open-world operation. The description adds useful context that it is a quote-reply and that scope includes group and private messages. It does not explain delivery behavior, permissions, or rate limits beyond the annotations.

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 description is two compact sentences with no wasted wording. The core operation and supported message scope are front-loaded, followed by the optional mention behavior.

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 simple quote-reply tool with complete parameter documentation and annotations covering the safety profile, the description provides enough context to invoke it correctly. It could be richer about how the quoted message appears or any permission requirements, but no essential calling information is missing.

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 parameters are already fully documented. The description reinforces that the reply is by message_id and that the sender can optionally be mentioned, but it does not add syntax or constraints beyond the schema. This meets the baseline for a fully documented schema.

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: quote-reply to a message by message_id. It also clarifies the supported scope, group and private messages, so an agent can identify the operation without opening the schema. It does not explicitly distinguish itself from send_message, which keeps it from a 5.

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 definition implies when to use it by saying it is a quote-reply keyed by message_id and works in group and private messages. It does not state when not to use it or name an alternative such as send_message. The optional mention behavior is explained, but routing guidance remains limited.

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