Skip to main content
Glama

click_inline_keyboard_button

Clicks an inline keyboard button in a QQ bot message. Use the message sequence (msg_seq) from the same button message, not the message ID, to trigger the button callback.

Instructions

点击内联键盘按钮 参数必须来自同一条机器人按钮消息;msg_seq 是消息序号,不是 message_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>",
      "bot_appid": "<bot_appid>",
      "msg_seq": "<msg_seq>",
      "button_id": "<button_id>"
    },
    "name": "click_inline_keyboard_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
msg_seqYes
group_idYes群号
bot_appidYes
button_idYes
callback_dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/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. The description adds a genuinely useful behavioral constraint (values must be sourced from the same message) and a disambiguation of msg_seq versus message_id, but says nothing about what the click triggers on the bot side, error behavior, or reversibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses, action first and the critical constraint immediately after, with no filler. Every clause carries information an agent could otherwise get wrong.

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 5-parameter, open-world mutation tool with no output schema, the definition covers the highest-risk trap (msg_seq vs message_id) and the sourcing constraint. It omits the meaning of button_id and callback_data and what a successful click returns or triggers, so an agent still has gaps to guess at.

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 only 20% (only group_id carries '群号'), so the description carries real weight here, and it does resolve the single most dangerous ambiguity: msg_seq is a message sequence number, not a message_id. It leaves bot_appid, button_id and callback_data entirely unexplained, so it only partially compensates for the coverage gap.

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 states a specific verb+resource pair ('点击内联键盘按钮' / click inline keyboard button), which is precise enough for an agent to know exactly what interaction it performs. It does not, however, contrast itself with the similarly named sibling 'qq_click', leaving the boundary implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear precondition for use: the parameters must originate from the same bot button message, which prevents an agent from synthesizing arbitrary IDs. It stops short of stating when not to use it or which sibling to prefer, so it is context-rich but not a full routing rule.

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