Skip to main content
Glama

send_poke

Send a QQ poke to a user in a private chat or group, automatically routing to the group when a group ID is provided.

Instructions

拍一拍(群聊/私聊自动路由) 将 group_id 替换为当前账号可访问的群号。

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

Input Schema

NameRequiredDescriptionDefault
user_idYes
group_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive write, so the safety profile is known. The description adds the auto-routing rule and the access precondition on group_id, which is genuine context. It says nothing about rate limiting, what the target user sees, or what happens when the account lacks access to the group, all of which matter for a notification-style action.

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?

Very short and front-loaded with the action name and routing mode, which is good. The second sentence reads as an editing instruction to a human ('replace group_id with …') rather than a statement of meaning, making it slightly ambiguous as guidance for an agent.

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 two-parameter mutation with no output schema and zero schema coverage, the description should clarify both identifiers and the outcome. It covers group_id only, leaving the required user_id and the success/failure behavior unexplained, so an agent could route the wrong ID type.

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 only partially does. It explains group_id (a group number the current account can access) and implicitly contrasts it with private chat, but user_id — the only required parameter — is never mentioned, nor is the accepted integer-or-string form.

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 concrete action (拍一拍 / poke) and states the routing behavior explicitly: it auto-routes between group and private chat. That goes beyond the bare name. It does not differentiate itself from the closely related siblings poke, group_poke, and friend_poke, so an agent still has to guess which variant to pick.

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?

Usage is only implied: supplying group_id sends the poke to a group, omitting it falls back to private chat via user_id. The note that group_id must be a group the current account can access is a useful precondition. There is no explicit when-to-use-this-vs-siblings guidance and no stated exclusions or failure cases.

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