Skip to main content
Glama

bili_qr_poll

Polls Bilibili QR-code login status using the key from the initial login request, returning waiting, scanned, expired, or ok so clients can complete authentication.

Instructions

B站扫码登录第二步:轮询扫码状态。返回 waiting / scanned / expired / ok。

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": {
      "key": "<key>"
    },
    "name": "bili_qr_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesbili_qr_login 返回的 key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It usefully discloses the state machine (waiting / scanned / expired / ok), which is real behavioral information beyond the schema, but it omits key lifetime, whether the key is single-use, and what a successful 'ok' actually yields.

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?

Two tight sentences with the flow position front-loaded and the return states enumerated compactly. No filler, though the state list could have been paired with the action to take on each.

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?

Reasonable for a simple one-parameter poll tool, but with no output schema the description should say more about what 'ok' returns (credentials/cookies) and how long a key remains valid before 'expired'. The agent is left to infer the success payload.

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 coverage is 100% and the schema already says the key comes from bili_qr_login, so the description repeats rather than extends that meaning. Baseline 3 is appropriate for a single fully-documented parameter.

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 (poll) plus resource (QR scan status) and frames itself as step two of the login flow, which implicitly separates it from bili_qr_login. An agent can tell what it does, though the sibling is only referenced indirectly via the parameter description.

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

Usage Guidelines3/5

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

The 'step two' framing plus the key parameter tied to bili_qr_login implies this is called after bili_qr_login, and the listed states imply polling until a terminal state. However, no explicit guidance on polling cadence, when to retry, or when to stop and fall back to a fresh login is given.

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