Skip to main content
Glama

get_msg

Read-only

Retrieves a QQ message by message_id, refreshes image, voice, and video URLs when available, and returns the updated message object for reading or processing.

Instructions

获取消息 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。 Returns: 消息事件对象(去除 post_type/self_id,附带 real_id);逐个尝试刷新图片、语音和视频 URL,成功使用新地址,失败保留该段原地址并继续返回消息;地址更新时同步 raw_message。

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>"
    },
    "name": "get_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/destructive annotations: it discloses that the tool attempts to refresh image, voice, and video URLs one by one, falls back to the original segment on failure, and syncs raw_message when addresses change. It also documents the return shape (message event object with post_type/self_id stripped and real_id added), which an agent could not infer from annotations alone.

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 is front-loaded in the first clause, followed by sourcing/precondition notes, then a clearly separated Returns section. The returns sentence is long and clause-heavy, but every clause conveys non-obvious behavior given there is no output schema.

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, the description adequately covers the return value, including field omissions, real_id addition, and URL-refresh fallback semantics. It does not state what the agent receives when the message is not queryable in the account's store (error vs. empty), which is the one remaining gap for a single-message fetch.

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 coverage is 0% and the only constraint in the schema is 'not 0', so the description carries real weight: it explains where the message_id comes from and explicitly clarifies that negative values are legal. It does not address the integer-vs-string duality in the schema, leaving one ambiguity unresolved.

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?

States a specific verb+resource (获取消息 / get message) and immediately qualifies it as a lookup by a real message_id obtained from a message event or send result, which implicitly distinguishes it from the history/list siblings. It never names an alternative tool, so the differentiation is inferred rather than explicit.

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?

Gives concrete preconditions an agent needs before calling: the id must be a real message_id from an event or send result, negative values are valid, and the message must be retrievable in the current account's store. It stops short of stating when to prefer this over get_forward_msg or the *_msg_history siblings, so no true alternatives 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