Skip to main content
Glama

send_group_notice

Publish QQ group announcements with options for pinning, popups, new-member targeting, read confirmation, and group-nickname prompts to notify members via an AI-operated QQ account.

Instructions

发送群公告(支持置顶、弹窗、新成员、群昵称引导与确认) 需要群公告管理权限;普通公告 type=1,新成员公告 type=20。 Rules: type must be 1 (regular) or 20 (new members); send_to_new_members conflicts with type.

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

Input Schema

NameRequiredDescriptionDefault
typeNo发布类型:1=普通公告,20=新成员公告;建议使用 send_to_new_members
imageNo可选公告图片(本地路径、URL 或 base64)
pinnedNo是否置顶:1=置顶,0=不置顶
contentYes公告正文
group_idYes群号
tip_window_typeNo弹窗展示:0=开启弹窗,1=关闭弹窗(QQ 原始字段为反向语义)
confirm_requiredNo是否需要群成员确认收到:1=是,0=否
is_show_edit_cardNo是否引导群成员修改群昵称:1=是,0=否
send_to_new_membersNo是否在成员新加入群时发送(与 type=20 等价)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish that this is a non-destructive write in an open world. The description adds an authorization requirement and the send_to_new_members/type conflict, both of which are real value beyond the annotations, but it does not disclose what happens on conflict or what an unsuccessful send looks like.

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 type rule (1=regular, 20=new members) is stated twice, once in Chinese and again in the English 'Rules' line, which wastes space. The feature list parenthetical is front-loaded and useful, but the duplicated constraint keeps the definition from being tight.

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 9-parameter mutation tool with no output schema, the description covers the essentials (permission, type values, one conflict rule) but is silent on return values, the meaning of the pinned/tip_window/confirm flags, and conflict resolution. It is adequate but leaves real gaps.

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 100%, so the baseline is 3. The description contributes one non-obvious rule beyond the schema: send_to_new_members conflicts with type, which the schema itself does not state. Otherwise its type explanation repeats the schema's enum text.

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?

It uses a specific verb and resource (发送群公告) and names the feature set it covers (置顶, 弹窗, 新成员, 确认). Siblings such as get_group_notice and del_group_notice make the create-vs-read-vs-delete distinction inferable, but it never explicitly says 'this creates a new notice'.

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?

It states the prerequisite (需要群公告管理权限) and when to use type=1 versus type=20, which is genuine usage context. It does not say when not to call it (e.g., duplicate notices, rate limits) or point to an alternative for reading or deleting notices.

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