Skip to main content
Glama
Sign In
doubao-image-mcp

doubao-image-mcp

by haikuotianko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

doubao_ping

Verifies whether the current Doubao account login session is valid and checks for IP risk controls before generating images.

Instructions

检查当前账号登录态是否有效（顺带判断是否被 IP 风控）。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
accountNo
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The description provides important behavioral context beyond basic status checking by explicitly mentioning that it also determines if the account is subject to IP risk control. This is critical for debugging or usage monitoring.

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?

The description is highly concise, using one single, impactful sentence to describe both primary functions of the function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

As a simple status and health-check tool with no parameters, the description covers all necessary information to correctly invoke and interpret the basic function of the tool.

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?

Since the tool has zero parameters and 100% schema coverage, the description meets the baseline of providing sufficient semantic context without needing to elaborate on empty fields.

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 clearly states the two functions of the tool: checking login validity and assessing IP risk control. While it doesn't name any specific resource, it distinguishes itself from the sibling 'doubao_login' by implying a status check rather than an initiation of a session.

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 description implies that the tool is used for health checks or verifying current session status. It provides minimal guidance on *when* to use it, but its function is clear from the name and context.

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