Skip to main content
Glama

set_doubt_friends_add_request

Approve or reject a suspicious QQ friend request using the flag returned by the doubt request lookup, with an optional approve setting to control the decision.

Instructions

处理可疑好友申请 flag 使用 get_doubt_friends_add_request 返回项的 uid。

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

Input Schema

NameRequiredDescriptionDefault
flagYes
approveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so this is a non-destructive write that touches external state — but the description adds nothing about what 'handle' actually does (approve adds a friend? reject ignores?), nor what happens if `approve` is omitted and defaults to true. For a mutation tool with this much ambiguity, this is a significant gap.

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?

One short sentence with no wasted words, but the brevity reflects under-specification rather than precision. The key actionable behavior (approve vs. reject) is simply absent.

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 state-mutating tool with no output schema, 0% parameter coverage, and an undocumented branch parameter, the description should clarify outcomes and the effect of `approve`. Instead it covers only the origin of one parameter.

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%, so the description must compensate. It usefully explains where `flag` comes from (the uid of a get_doubt_friends_add_request return item), but it says nothing about `approve`, the parameter that determines whether the request is accepted or rejected — a critical semantic left entirely to the schema's default value.

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 (可疑好友申请 / suspicious friend requests) and identifies a specific sibling (get_doubt_friends_add_request) as the source of the flag. However, the verb '处理' (handle/process) is vague — it doesn't say whether the tool approves, rejects, or both, even though an `approve` parameter exists.

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 gives an important prerequisite: the `flag` is the uid taken from a get_doubt_friends_add_request response item, which tells the agent the correct call sequence. It does not distinguish this tool from siblings like set_friend_add_request or explain when rejection vs. approval is appropriate.

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