Skip to main content
Glama

poke

Send a QQ nudge to a friend in private chat or to a group member; provide the user ID and optional group ID to target the right conversation.

Instructions

戳一戳 someone: a friend in private chat, or a member inside a group.

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

Input Schema

NameRequiredDescriptionDefault
user_idYesQQ number to poke
group_idNoGroup to poke them in (omit for private poke)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds almost nothing beyond that: it does not say whether the poke notifies the recipient, whether friendship is required, or how failures (non-member, non-friend) behave. The private/group distinction it does mention is duplicated in the schema parameter descriptions.

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?

A single short sentence with zero filler, and the target/mode information is front-loaded. It is efficient, though its brevity borders on under-specification for a tool with two distinct invocation modes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with full schema coverage and annotations present, the description is minimally sufficient to call correctly. It leaves open what a poke actually does to the recipient and any permission or friendship constraints, which an agent may need before invoking it.

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?

Schema description coverage is 100%, so both user_id ('QQ number to poke') and group_id ('omit for private poke') are already documented. The description's 'friend in private chat, or a member inside a group' restates that same private/group split without adding format, range, or edge-case meaning. Baseline 3 applies when the schema does the heavy lifting.

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 pairs the verb 'poke' with a clear resource and scope, stating it targets 'a friend in private chat, or a member inside a group.' This lets an agent tell it acts on a person rather than a message or group object. It stops short of naming which sibling (e.g. friend_poke or group_poke) handles each mode.

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: the two modes ('friend in private chat', 'member inside a group') suggest when each applies, but the description never says explicitly to use this versus the sibling poke tools, nor does it state prerequisites such as being friends with the target.

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