Skip to main content
Glama

set_friend_add_request

Approve or reject incoming QQ friend requests by passing the original request flag; set approve to false to decline. Use the flag exactly as received from the request event.

Instructions

处理好友添加请求 flag 必须原样使用当前账号好友请求事件的 flag,不能根据 QQ 号构造。

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_friend_add_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagYes
approveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already disclose the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely non-obvious behavioral context: the flag must be used verbatim from the current account's friend-request event and cannot be synthesized from a QQ number. That prevents a realistic failure mode. It stops short of explaining what approve=true/false actually does or what the call returns.

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?

Two compact clauses with no filler, and the purpose is front-loaded before the flag constraint. The terseness of the opening half-sentence ('处理好友添加请求') slightly undercuts clarity, but nothing is wasted.

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 two-parameter mutation tool with no output schema and zero schema coverage, the description covers the risky parameter well but leaves the approve semantics, the effect of the call on the pending request, and the response behavior unexplained. Adequate to avoid the flag misuse, not fully adequate overall.

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 description coverage is 0%, so the description carries the burden, and it explains the flag parameter meaningfully (its provenance and that it cannot be constructed). However, the second parameter approve (boolean, default true) is never mentioned, so the agent must infer from the name what TRUE/FALSE will do to the request.

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 (好友添加请求, friend add request) and a generic verb (处理, 'handle'), but never says what handling means — approving, rejecting, or both depending on the approve flag. It also gives no differentiation from the sibling set_doubt_friends_add_request, which handles a closely related request type.

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 when-to-use guidance: no statement that this applies only to friend requests (as opposed to group requests, handled by set_group_add_request), no mention of the doubt-friend variant as an alternative, and no prerequisites. The only guidance is a data-integrity constraint on the flag argument, not on tool selection.

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