Skip to main content
Glama

set_group_add_request

Approves or rejects QQ group join and invitation requests using the event flag, with optional reason and request subtype handling.

Instructions

处理加群请求 flag 和 sub_type 原样取自同一条群请求事件;邀请事件使用 invite。

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": {
      "flag": "<flag>"
    },
    "name": "set_group_add_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagYes
typeNo
reasonNo
approveNo
sub_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations mark this as a non-read-only, open-world, non-destructive mutation, so the description carries most of the burden. It adds a useful provenance constraint (flag and sub_type must come from the same event), but never states the effect of approving versus rejecting, whether `reason` is surfaced to the requester, or whether the action is reversible.

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 text is short and front-loads the tool's subject, with no filler. But the terseness comes at the cost of coverage, so it reads as under-specified rather than efficiently complete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation tool with no output schema and zero schema description coverage, the description should cover at least the approve/reject semantics and reason handling. As written, an agent could not confidently choose `approve` or supply `reason` without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, so the description must compensate. It explains only `flag` and `sub_type` (2 of 5), leaving `approve` (the core decision, defaulting to true), `reason`, and `type` completely undocumented in both schema and description.

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

Purpose3/5

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

The description names the resource (加群请求 / group join request) and a verb (处理 / handle), so the domain is identifiable. However, '处理' is vague about the actual action, which, judging by the `approve` flag, is approving or rejecting a pending request. Nothing distinguishes it from siblings such as set_friend_add_request or get_group_ignore_add_request.

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?

The only guidance is a value-level hint that invite events use `sub_type` = "invite". There is no statement of when to use this tool versus the friend-add or doubt-friends variants, and no mention of how `flag` is obtained, aside from saying it must come from the event.

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