Skip to main content
Glama
haoan33

OmniQQ-MCP

by haoan33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_qq_accounts

Read-onlyIdempotent

Retrieves cached QQ accounts, default active account, and online status to check which logged-in accounts can be switched to without scanning a QR code.

Instructions

读取本地沙箱中所有已缓存登录凭证的 QQ 账号列表、当前默认激活账号及当前在线账号详情。 适用场景：在切换账号前查询有哪些历史已登录 QQ 号可供免扫码切换。不适用与替代：若仅需确认当前在线账号的 user_id 和昵称，请改用 get_login_info；若需同时检查运行时安装与 GitHub 版本更新，请改用 check_napcat_environment。 行为与返回：纯只读无副作用操作；返回 service_running、online_account、default_account 与 cached_accounts 数组。列表中的账号可直接传给 switch_qq_account 热切换。

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNo接口返回的业务负载数据（对象或数组，具体字段依工具而定）
statusNo执行状态标识，成功为 'ok'（或特定生命周期状态），失败为 'failed' 或 'error'
messageNo状态说明或错误诊断详情
retcodeNoOneBot 11 响应状态码，0 表示成功，非 0 表示协议端或网络错误

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "description": "接口返回的业务负载数据（对象或数组，具体字段依工具而定）"
+    },
+    "message": {
+      "description": "状态说明或错误诊断详情",
+      "type": "string"
+    },
+    "retcode": {
+      "description": "OneBot 11 响应状态码，0 表示成功，非 0 表示协议端或网络错误",
+      "type": "integer"
+    },
+    "status": {
+      "description": "执行状态标识，成功为 'ok'（或特定生命周期状态），失败为 'failed' 或 'error'",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changedv1.1.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description restates the read-only/no-side-effect profile rather than adding much beyond it. However it does add non-obvious value by naming the four returned fields and, critically, noting that returned accounts can be fed directly into switch_qq_account as a hot switch — a cross-tool interop fact not present in any structured field.

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?

The description is organized into clearly labeled blocks (purpose, usage, exclusions, behavior/returns) with the core verb-resource statement front-loaded. There is mild redundancy in enumerating the return fields when a full output schema already exists, but nothing is bloated.

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

Completeness5/5

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

For a zero-parameter read tool with full annotations and an output schema, the description covers everything an agent needs: what it returns, that it is side-effect free, when to prefer it, and how its output connects to switch_qq_account. No gaps remain that would cause a misinvocation.

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?

The tool takes zero parameters and the schema correctly declares an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline for a no-param tool is 4; no parameter guidance is necessary or missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reading the cached-credential QQ account list plus default and online account state from the local sandbox. It also explicitly distinguishes itself from get_login_info and check_napcat_environment, so an agent can pick the right tool without opening schemas.

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

Usage Guidelines5/5

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

The 适用场景 line names the exact precondition (querying historically logged-in accounts before a switch) and the 不适用与替代 line routes two concrete alternatives to their specific conditions. This is explicit when-to-use and when-to-use-something-else guidance.

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