Skip to main content
Glama

doubao_status

Checks Doubao browser, login, and verification status, then returns the supported model parameters while opening a separate Doubao tab.

Instructions

检查豆包浏览器、登录或验证状态,返回支持的调用模型参数。会创建独立豆包标签页。

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important non-obvious side effect: a separate Doubao tab is created. It does not say whether that tab persists or closes, what happens if login/verification fails, or whether the call blocks on user interaction — meaningful gaps for a tool that touches a browser session.

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 short sentences, front-loaded with the primary purpose and followed by the side-effect warning. No filler, though the second sentence about the tab could be merged more tightly with the first.

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 status tool with no output schema, the description should at least sketch the shape of the result (status values, the model parameter list) and failure modes such as not-logged-in. It hints at the return payload but leaves the agent unable to anticipate what it will receive or how to react to a failed verification.

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 nothing for the description to disambiguate; baseline 4 applies. The schema is fully closed (additionalProperties false) and needs no narrative support.

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+resource: check Doubao browser/login/verification status, and adds that it returns supported invocation model parameters. This is clearly distinguishable from the sibling doubao_generate_image. The only weakness is that 'status check' and 'return model parameters' are two slightly different purposes bundled without clarifying the relationship.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance, no mention of prerequisites (e.g. must be logged in), and no statement of when not to call it or what to do with the returned model parameters. The agent must infer that this is a preflight check before generation.

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