Skip to main content
Glama
pushplus

PushPlus MCP Server

Official
by pushplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

新增 QQ 机器人配置

open_qqbot_add

POST /open/qqBot/add - 新增 QQ 机器人配置：发到指定QQ群(sendType=2)，或用指定机器人发给自己(sendType=1)。 只用默认机器人发给自己时无需配置。 请求: qqName(配置名称,必填,最多64字符), qqCode(配置编码,必填,最多32字符,仅字母/数字/下划线/中划线,创建后不可修改), sendType(1发给自己/2发到QQ群,可选,默认2), qqGroupId(QQ群编号,sendType=2时必填,取自…

Instructions

POST /open/qqBot/add - 新增 QQ 机器人配置：发到指定QQ群(sendType=2)，或用指定机器人发给自己(sendType=1)。 只用默认机器人发给自己时无需配置。 请求: qqName(配置名称,必填,最多64字符), qqCode(配置编码,必填,最多32字符,仅字母/数字/下划线/中划线,创建后不可修改), sendType(1发给自己/2发到QQ群,可选,默认2), qqGroupId(QQ群编号,sendType=2时必填,取自 groupList 的 id；该群需允许机器人主动消息), botAppId(机器人appId,sendType=1时必填且需已绑定；sendType=2时可不填,以群所在机器人为准)。 限制: 同一QQ群、同一机器人的“发给自己”均不可重复创建。 统一响应: code(数字,200成功), msg(字符串), data(业务数据)。

Input Schema

NameRequiredDescriptionDefault
qqCodeYes配置编码，最多32个字符，仅字母、数字、下划线和中划线
qqNameYes配置名称，最多64个字符
botAppIdNo发送使用的机器人appId，sendType=1时必填
sendTypeNo发送类型：1发给自己，2发到QQ群；默认2
qqGroupIdNoQQ群编号，sendType=2时必填，取自 open_qqbot_group_list 的 id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.0
    • addedInput schema / properties / botAppId
      Added value: +{
+  "description": "发送使用的机器人appId，sendType=1时必填",
+  "type": "string"
+}
    • changedInput schema / properties / qqGroupId / description
      Previous value: -"QQ群编号，取自 open_qqbot_group_list 的 id"New value: +"QQ群编号，sendType=2时必填，取自 open_qqbot_group_list 的 id"
    • addedInput schema / properties / sendType
      Added value: +{
+  "description": "发送类型：1发给自己，2发到QQ群；默认2",
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[
-  "qqName",
-  "qqCode",
-  "qqGroupId"
-]New value: +[
+  "qqName",
+  "qqCode"
+]
  2. First observedv1.0.9

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the uniqueness constraint against duplicate creation, that qqCode is immutable after creation, that the group must permit proactive bot messages, and that botAppId must already be bound. It omits any auth/permission requirement or rate-limit context, keeping it short of a 5.

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?

Front-loaded with the HTTP route and one-line purpose, then structured into 请求 / 限制 / 统一响应 blocks, so an agent can scan to the relevant clause. It is dense and repeats some facts already present in the schema (e.g. qqCode character rules), which costs it a point.

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

Completeness4/5

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

No output schema exists, and the description compensates by documenting the response envelope (code/msg/data). Combined with per-parameter conditions and the duplicate-creation restriction, the definition is nearly complete; only authentication and error-case behavior are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description adds real value on top by spelling out cross-field conditions (qqGroupId required only when sendType=2, botAppId required only when sendType=1 and ignored otherwise, group's bot takes precedence for sendType=2) and format/immutability rules for qqCode.

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?

States a specific verb and resource (新增 QQ 机器人配置) and immediately explains the two operating modes (sendType=1 to self, sendType=2 to a QQ group) plus the no-config-needed case. However, it never distinguishes this tool from nearby siblings like open_qqbot_edit or open_qqbot_custom_bot_add, which an agent could easily confuse with 'add a QQ bot'.

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?

Provides clear conditional usage for each sendType and a genuine when-not-to-use hint ('只用默认机器人发给自己时无需配置'). It stops short of routing to alternatives (e.g. open_qqbot_edit for modification, open_qqbot_list for enumeration), which would make it a 5.

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