Skip to main content
Glama
Sign In
volcengine-seedream-img-mcp

volcengine-seedream-img-mcp

by ckz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_image_result

Check the status of a submitted image task using its request ID. Returns pending, succeeded, or error state.

Instructions

Poll the result of a previous generate_image, edit_image, or generate_image_group call. Returns state: pending | succeeded | error.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_image_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesUUID returned by a submit tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description must carry burden. It discloses return states, but does not mention whether the call is read-only, safe, idempotent, or any rate limits. The safety profile is not explicitly stated.

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, no redundant words. The first sentence states purpose and scope, the second lists return states. Efficient and front-loaded.

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 polling tool with one parameter and no output schema, the description explains purpose and states. However, it omits behavioral details like read-only nature and does not fully describe the response structure beyond state.

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?

Schema coverage is 100% and schema description says 'UUID returned by a submit tool.' The tool description adds value by specifying the exact submit tools (generate_image, edit_image, generate_image_group), making it more precise.

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 polls results from three sibling tools, includes the verb 'poll', and specifies the resource (image generation result). This distinguishes it from the creation tools.

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?

Explicitly tells when to use: after calling generate_image, edit_image, or generate_image_group. It implies the polling context, but does not provide when-not-to-use or alternative strategies.

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