Skip to main content
Glama

delete_friend

Destructive

Deletes a specified QQ friend by user ID, with an option to block them, so you can remove unwanted contacts from your account when removal is explicitly needed.

Instructions

删除好友 会删除指定好友;仅在明确需要删除时调用。

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": {
      "user_id": "<user_id>"
    },
    "name": "delete_friend"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockNo
user_idYesQQ 号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is structured data. The description adds a caution to only invoke when deletion is clearly intended, but says nothing about whether the deletion is one-way (only from the caller's list), whether it is reversible, or what happens to an already-sent friend request.

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 short sentences, front-loaded with the action and followed by a conditional guard, with no filler. It is arguably too terse given the destructive nature, but nothing is wasted.

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 destructive social-graph mutation with no output schema and a half-documented parameter set, the definition leaves key questions open: the effect of `block`, whether deletion is mutual, and what a failure looks like. It does not fully arm the agent to call the tool correctly and safely.

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 coverage is 50%: user_id carries a description ("QQ 号") while the `block` boolean is undocumented in both schema and description. The description never explains that deleting can optionally block the person, which is exactly the semantic the agent needs before choosing a value.

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?

The description names a specific verb and resource ("删除好友" – delete friend) and repeats the scope ("删除指定好友"), so the agent knows exactly which object is affected. It does not differentiate from the many sibling delete_* tools, but the resource noun (friend vs. message/group file) does that implicitly.

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?

"仅在明确需要删除时调用" gives a caution condition (call only when deletion is explicitly required), which is genuine when-to-use guidance for a destructive tool. However, it offers no alternatives (e.g., unfriending vs. blocking vs. ignoring) and no prerequisites such as whether the target must already be in the friend list.

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