Skip to main content
Glama
OmniQQ-MCP

OmniQQ-MCP

by haoan33

get_login_qrcode_image

Read-onlyIdempotent

Retrieves the local path of the latest cached NapCat login QR code image and optionally opens it on the desktop to re-view a previously generated QR code.

Instructions

读取本地缓存的最新 NapCat 登录二维码图片路径 (qrcode.png),并可选在桌面弹出展示该图片。 适用场景:当 login_new_qq_by_qrcode 已经生成二维码但用户关闭了图片窗口需要重新查看时调用。不适用与替代:本工具不会启动扫码进程或刷新过期二维码;如需发起新的扫码会话,请改用 login_new_qq_by_qrcode。 行为与返回:只读查询本地文件状态(open_image=True 时触发本地图片查看器);文件存在返回 status='ok' 与 qrcode_path,不存在返回 status='not_found'。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_login_qrcode_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
open_imageNo若本地二维码图片文件存在,是否在 Windows 桌面立即打开图片查看器展示,默认 True

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • changedInput schema / properties / open_image / description
      Previous value: -"若二维码文件存在,是否立即在屏幕上打开图片查看器,默认 True"New value: +"若本地二维码图片文件存在,是否在 Windows 桌面立即打开图片查看器展示,默认 True"
    • 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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true; beyond those, the description adds that the tool only reads local file state, that open_image=True launches the local image viewer, and that it never refreshes an expired QR code. The return-status values ('ok'/'not_found') are also mentioned, though an output schema already covers them, so the value added is real but partly redundant.

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 front-loaded: it states the purpose, then covers scenarios, exclusions and return behavior in labelled groups. However, the 'behavior and returns' sentence partly repeats what the output schema already provides, so not every sentence adds new information.

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 single-parameter read-only tool with full annotation coverage and an output schema, every question an agent could have about calling this tool correctly is answered: what it reads, what the flag does, when not to use it, and what the outcomes are. Nothing material is missing.

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 has one parameter with 100% description coverage already stating that open_image controls whether the Windows viewer opens. The description restates the same condition ('open_image=True 时触发本地图片查看器') without adding format or edge-case detail, so the schema is doing the work and the baseline of 3 applies.

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?

The first sentence states a specific verb and resource: read the cached path of the latest NapCat login QR image (qrcode.png) and optionally display it. It explicitly distinguishes this from login_new_qq_by_qrcode, so an agent can tell the two apart without opening either schema.

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 description names the exact situation in which to use the tool ('login_new_qq_by_qrcode generated a QR code but the user closed the image window') and the opposite case ('does not start a scan session or refresh an expired QR code'), and it routes the agent to the right alternative for a new session.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.