redfox-mcp

Official

Overview Schema Source Related Servers Discussions Admin

doubao_image_lite_result

Retrieve results from a Seedream 5.0 Lite image generation task. Use this tool when a previous generate request returns a task ID, to obtain the final output.

Instructions

查询 Seedream 5.0 Lite 任务结果。仅在 doubao_image_lite_generate 超时返回 taskId 后使用。

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": {
      "task_id": "<task_id>"
    },
    "name": "doubao_image_lite_result"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 18, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'query result' without explaining error behavior, idempotency, or what happens if the task is still pending. For a polling tool, expected details like 'returns status and result when ready' are missing.

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: first states purpose, second defines usage condition. No extraneous words, front-loads the core function. Ideal conciseness for a simple tool.

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?

Given a single required parameter and the presence of an output schema, the description is partially complete. It covers purpose and usage context but omits parameter explanation and behavioral nuances like error handling. The agent can infer the taskId source from the usage note but not explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the input schema lacks any description for the 'task_id' parameter. The tool description does not mention the parameter or explain its expected format or source, failing to add any semantic value beyond the raw schema.

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?

The description clearly states it queries the result of a Seedream 5.0 Lite task. The verb '查询' (query) and resource '任务结果' (task result) are specific. It distinguishes itself from sibling tools like 'doubao_image_pro_result' and 'doubao_video_result' by referencing the specific model and generator tool.

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

Usage Guidelines5/5

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

Explicitly states when to use: '仅在 doubao_image_lite_generate 超时返回 taskId 后使用' (only after doubao_image_lite_generate times out and returns a taskId). This provides clear context for invocation and implies not to use it before generation completes or for other tasks.

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

Deploy Server