Skip to main content
Glama

qq_login

Read-only

Logs in to QQ by showing a QR code screenshot to scan and confirm, or by clicking a remembered account button, then verifies login status.

Instructions

Log in to QQ. If not logged in, returns a screenshot of the QQ login window: show the QR code to the user and ask them to scan it with the QQ phone app (扫一扫) and confirm on the phone. If the window shows a "登录"/"进入QQ" button for a remembered account instead, click it with qq_click. Call qq_login_status afterwards (or wait=true here).

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

Input Schema

NameRequiredDescriptionDefault
waitNoAfter showing the screen, wait up to 120s for the login to complete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered structurally. The description adds genuinely non-obvious behavior: the tool surfaces a window for human interaction rather than authenticating silently, requires the user to act on their phone, and defers the remembered-account button press to another tool. What it omits is what a successful return looks like versus the screenshot case.

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?

Four tight sentences, front-loaded with purpose before the procedural branches, and none is filler. Minor redundancy remains: the 120s wait bound and the wait-for-completion concept appear in both the schema and the description.

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?

For a one-optional-parameter tool with no output schema, the definition supplies what an agent actually needs: the returned artifact (a screenshot), the human step required, and the follow-up call. The only gap is the non-screenshot success path, which is left unspecified.

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 100% and the single `wait` parameter is fully described there, so baseline would be 3. The description earns above baseline by framing `wait=true` as an alternative to a separate qq_login_status call, which tells the agent the two approaches are interchangeable rather than sequential.

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 opening sentence names a specific verb and resource ("Log in to QQ") and the remaining text makes the tool's outcome concrete: it returns a screenshot of the login window rather than performing authentication itself. It is clearly distinguishable from qq_login_status (status polling) and qq_click (button interaction), both of which are named directly.

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 definition gives explicit conditional routing: if not logged in, show the QR code and have the user scan it via 扫一扫; if a "登录"/"进入QQ" button appears for a remembered account, use qq_click instead; then call qq_login_status or pass wait=true. This covers when-to-use, the branch that selects a sibling tool, and the correct follow-up call.

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