Skip to main content
Glama

doubao_login

Opens a QR-code login window so you authenticate with the Doubao App. Call it when no account exists, a session expires, or image generation reports a not-logged-in error.

Instructions

弹出扫码登录窗口,让用户用豆包 App 扫码。没有账号、登录态失效、或 doubao_image 报「未登录」时调用它。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
accountNo
messageYes
nicknameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it reveals that this is an interactive UI action requiring a human to scan with a physical device, which is the single most important behavioral fact for an agent deciding to call it. It does not say whether the call blocks until scanning completes or how it fails if the user ignores the window, but the presence of an output schema reduces the need to describe results.

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 sentences: the first states the action and the human interaction it requires, the second lists trigger conditions. No filler, and the action is front-loaded ahead of the routing guidance.

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 zero-parameter tool with an output schema, the description covers what it does, who must act, and when to invoke it. The only meaningful gap is blocking/timeout behavior during the QR scan, which an agent would want to know before invoking a modal.

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, which is the baseline-4 case, and the description correctly implies no input is required — the agent supplies nothing, the user supplies the scan. No parameter meaning is lost.

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?

The description states a specific action and resource: popping up a QR-code login window for the user to scan with the Doubao App. This is far more specific than a bare 'login' label. It distinguishes itself from doubao_image by naming that sibling as a trigger source, though it does not contrast with doubao_accounts or doubao_verify.

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?

Three concrete when-to-use conditions are given: no account, expired session, or doubao_image reporting 'not logged in'. This is clear context routing. No explicit when-not-to-use or prerequisite ordering (e.g., call this before retrying doubao_image) is stated.

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