Skip to main content
Glama

friend_poke

Sends a QQ friend poke to a specified contact so you can notify or get their attention without writing a message.

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

Input Schema

NameRequiredDescriptionDefault
user_idYes
target_idNo

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 already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this is a non-destructive but state-changing outbound action. The description adds nothing beyond that: no note that the poke notifies the target, no rate/frequency limits, no visibility or permission requirements.

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?

It is short and front-loaded, but the two halves ('好友拍一拍' and '戳一戳指定好友') are near-duplicates of each other and of the tool name, so the second sentence earns little beyond the first.

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?

There is no output schema, so the description does not need to cover return values, but for a two-parameter action tool with zero schema documentation it leaves both parameter roles and expected effect on the target unexplained. An agent could not reliably call this correctly from the description alone.

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 carry parameter meaning, and it does not. Two ID-like parameters (user_id, target_id) are present, but the description only vaguely says 'specified friend' and never clarifies which parameter is the sender versus the poke recipient.

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 gives a verb+resource ('戳一戳指定好友' / poke a specified friend), so the basic action is identifiable. However, it largely restates the tool name 'friend_poke' and offers no differentiation from siblings such as poke, send_poke, or group_poke that plausibly compete for the same intent.

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 prerequisites (e.g., must already be friends), and no mention of alternatives. Usage is only implied by the word '好友' (friend), which hints at the friend-scoped variant without saying so explicitly.

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