Skip to main content
Glama

bili_qr_login

Generate a Bilibili QR login short link as the first step, then check scan results with bili_qr_poll.

Instructions

B站扫码登录第一步:拿二维码短链。第二步用 bili_qr_poll 等扫码结果。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of explaining behavior. It hints that the return value is a '短链' (short link), but it says nothing about QR expiry, whether re-calling invalidates an earlier code, rate limits, or what happens if polling never occurs. For a login-flow tool whose side effects matter, this is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences cover both the step number and the next action. The sequencing constraint is front-loaded, and no wording is wasted.

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?

For a zero-parameter tool with no output schema, the definition covers the workflow position but leaves the return shape vague: 'short link' without saying whether the response also includes a token or expiry. It is adequate for invocation, but it could easily state more about credentials and the lifetime of the code.

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, so there is no parameter semantics for the description to explain; the baseline is 4. Nothing about the empty input schema needs elaboration.

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?

It states a specific action plus resource: '拿二维码短链' (get the QR-code short link) for Bilibili QR login, and labels it as step one. It also distinguishes this tool from the sibling bili_qr_poll by assigning that tool the polling role, so an agent can tell the two apart without reading 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 Guidelines4/5

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

It clearly places the tool in a workflow: call this first to get the QR link, then use bili_qr_poll to wait for the scan result. It gives clear context and names the alternative, but it does not say when not to use it, for example whether this only applies to unauthenticated login or whether a user already logged in should skip this step.

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