Skip to main content
Glama

group_poke

Sends a poke to a specified QQ user in a group using the group ID and QQ number, enabling targeted group chat interaction.

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

Input Schema

NameRequiredDescriptionDefault
user_idYesQQ 号
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this action has side effects and reaches external recipients. The description adds nothing beyond that: it mentions no rate limits, notifications, member requirements, or how the action behaves toward the poked user, which for an action that sends a poke is a real 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?

The single short sentence is front-loaded and has no wasted wording, but its brevity comes from leaving information out rather than from compressing it. There is no structure that would help an agent decide whether to invoke the tool.

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 an action tool with two required parameters, no output schema, and only partial annotation coverage, the definition should explain the effect on the target user and the membership or permission requirements. The tool does not do that, so the agent must guess how the poke behaves and what result to expect.

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?

The schema describes both parameters at 100% coverage (user_id = QQ number, group_id = group number), so the description's note that the group must be accessible to the current account adds only a small amount of meaning. Nothing is said about user_id, which is the poke target, or about whether the target must already be a group member.

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 essentially restates the tool name: "群拍一拍" (group poke) names a verb and a resource, and the "群" prefix does separate it from the siblings friend_poke and poke. However, it never says what a "poke" actually does and gives no further detail about scope.

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?

The only guidance is an instruction to replace group_id with a group number that the current account can access, which is a hint about a parameter rather than a rule for when to use this tool. It never says when to choose this tool over poke, friend_poke, or send_poke, so the agent has to rely only on the names of those sibling tools.

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