Skip to main content
Glama

send_group_msg

Send text or message segments to a specified QQ group by group number and receive the resulting message ID.

Instructions

发送群消息 替换目标群号;成功返回的 message_id 可为负值。 Returns: { message_id: number }

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": {
      "group_id": "<group_id>",
      "message": "<message>"
    },
    "name": "send_group_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesOneBot message: string | segment[] | object. In segment arrays, text segments whose text field is exactly "" are compatibility placeholders and do not count as sendable segments; missing, null, and whitespace-only text remain subject to normal validation.
group_idYes群号
auto_escapeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive write. The description adds two pieces of genuinely useful behavior beyond them: the return shape (message_id) and the quirk that a successful message_id may be negative, which would otherwise mislead an agent checking for failure. It omits permission requirements, rate limits, and failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is short and front-loads the purpose, so nothing is padded. However, the middle clause is a garbled fragment and the definition mixes languages, which costs clarity rather than wasting length.

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 three-parameter send tool with no output schema and only partial annotation coverage, the description supplies the return value and the negative-id caveat, which is the most important missing context. It still leaves out error behavior and whether the caller needs group membership or bot permissions, so it is adequate but incomplete.

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 coverage is 67%, with group_id and especially message well documented in the schema itself, while auto_escape is undocumented there. The description's only parameter-related content is the ambiguous '替换目标群号' phrase, which adds little and does not compensate for the auto_escape gap, but the schema carries most of the burden.

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 opening phrase '发送群消息' gives a clear verb plus resource, so an agent knows this sends a message to a group. It does not differentiate from siblings such as send_msg, send_group_forward_msg, or send_group_notice, so the agent must rely on the name to resolve that ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this versus send_msg or the other group-oriented send siblings, and no prerequisites or exclusions. '替换目标群号' is a terse fragment that does not clarify the calling context.

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