Skip to main content
Glama

get_group_notice

Read-only

Fetches announcements for a QQ group, merging standard and new-member notices into a single array with member-target flags and image metadata.

Instructions

获取群公告 将 group_id 替换为当前账号可访问的群号。 Returns: 普通公告与新成员公告的合并数组;send_to_new_members 标识后者;图片含 id、url、宽高

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes further by disclosing the return shape: a merged array of regular and new-member notices, with send_to_new_members distinguishing the latter and image entries carrying id, url, width and height. That is real behavioral context an agent cannot get from the annotations or schema.

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 phrase, followed by the parameter constraint and then the return description, in a compact block with no filler. The bilingual switch between the action sentence and the "Returns:" clause is slightly jarring but not wasteful.

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 one required parameter, full schema coverage, no output schema and read-only annotations, the description covers what the tool does, what input constraint applies, and what the response contains. Only the absence of any sibling/alternative routing keeps it from being fully complete.

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 100% and the parameter already documents "群号", so the baseline would be 3. The description adds meaning beyond the schema by constraining the value to a group the current account can access, which is an access-scope rule the schema does not encode.

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 pair and is unambiguously a read operation, which implicitly separates it from send_group_notice and del_group_notice. It stops short of naming those siblings explicitly, so an agent must infer the contrast from the verb alone.

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 prerequisite "将 group_id 替换为当前账号可访问的群号" tells the caller the group must be one the current account can reach, which is a genuine usage condition. However, there is no explicit when-to-use vs. alternative guidance (e.g., when to prefer get_group_notice over get_group_system_msg or get_group_ignored_notifies).

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