Skip to main content
Glama

del_group_notice

Destructive

Deletes a QQ group announcement using group ID and either fid or notice_id; requires admin permissions.

Instructions

删除群公告(fid 或 notice_id 二选一) notice_id 来自 _get_group_notice;删除需要管理权限。

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": "del_group_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
fidNo
group_idYes群号
notice_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the hazard is known; the description adds the non-obvious authorization requirement (admin permission) that an agent must satisfy before calling. It does not say whether deletion is recoverable or what an error looks like when the caller lacks admin rights.

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

Conciseness5/5

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

Three short clauses, each carrying a distinct fact (identifier choice, identifier provenance, permission requirement), with no filler or repetition of the tool name.

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?

For a destructive 3-parameter tool with no output schema and thin schema descriptions, the description covers the essentials: target, identifier selection, identifier source, and permission gate. Minor gap is the ambiguity of fid and the absence of failure/irreversibility guidance.

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 only 33% (only group_id is documented), so the description must compensate. It does: it explains that fid and notice_id are mutually exclusive alternatives and where notice_id comes from, which the schema does not state. It does not clarify what 'fid' refers to or what happens when both or neither are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('删除群公告' / delete group notice) and immediately constrains the identifier: exactly one of fid or notice_id. An agent can tell precisely what object this operates on without opening the schema.

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 the precondition ('删除需要管理权限' – requires admin permission) and the provenance of the identifier ('notice_id 来自 _get_group_notice'), which routes the agent to the right sibling for obtaining a notice_id. It does not name the complementary create/send tool or state what to do if permission is lacking.

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