Skip to main content
Glama

send_flash_msg

Sends a flash-transfer share message to a QQ private or group chat using a fileset_id, so recipients can download the referenced fileset.

Instructions

发送闪传消息(私聊或群聊,引用 fileset_id 让对端下载) fileset_id 来自 create_flash_task、get_fileset_id 或 list_filesets,替换为当前账号可访问的文件集。 会发送分享消息;message_id=0 是占位值,不能用于撤回或查消息。 Returns: { message_id }

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": {
      "fileset_id": "<fileset_id>"
    },
    "name": "send_flash_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idNo
group_idNo
fileset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses a genuinely useful behavior not present in the annotations: message_id=0 is a placeholder value that cannot be used for recall or message lookup, which directly affects what an agent should do with the return value. It also warns that this sends an actual share message. It does not mention permission requirements or rate limits, and its openWorldHint/destructiveHint behavior is already covered by 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and leads with the core action, then the fileset_id provenance, then the message_id caveat, then the return shape. Each sentence carries real information, though the run-on parenthetical structure could be broken up for readability.

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?

There is no output schema, but the description supplies the return shape ({ message_id }) and warns about the placeholder value, which covers the most important post-call behavior. The main remaining gap is how the three parameters interact, especially which of user_id/group_id to choose and whether the target must be reachable.

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 0%, so the description must compensate for three parameters: user_id, group_id, and fileset_id. It meaningfully explains fileset_id, including its source and accessibility requirement, and 'private or group chat' hints at user_id versus group_id. However, it never states that exactly one of user_id or group_id should be supplied, or what happens if both or neither are given, despite the schema requiring only fileset_id.

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: send a flash-transfer (闪传) message for a fileset, either privately or in a group. It names the upstream tools that produce fileset_id (create_flash_task, get_fileset_id, list_filesets), which separates this sending step from those preparation steps. It does not explicitly contrast itself with the generic send_msg, send_file, or send_private_msg siblings, so it falls short of 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 Guidelines4/5

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

It states a clear prerequisite: fileset_id must come from create_flash_task, get_fileset_id, or list_filesets, and must be a fileset the current account can access. The 'private or group chat' phrasing implies choosing user_id or group_id. It does not explicitly say when not to use this tool, for example instead of send_file or send_private_msg.

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