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

mclans-image-mcp

by YupegLV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

check_task

Query the status and result of an image generation task. Returns the local file path when the image is ready after automatic download.

Instructions

查询生图任务的状态和结果。后台 Worker 会自动轮询远程服务器并下载图片，无需手动轮询。任务完成后返回本地图片路径

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": {
      "taskId": "<taskId>"
    },
    "name": "check_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes任务 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 discloses the tool is a read-only query operation and that results include a local image path. It does not mention side effects, rate limits, or authentication, but is fairly transparent for a query tool.

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 concise with three short sentences, front-loading the purpose. No wasted words.

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?

The description lacks detail on response structure for in-progress states or errors. Since there is no output schema, more completeness would be helpful.

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

Parameters3/5

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

Schema coverage is 100% for the single parameter, so the description provides minimal added value beyond the schema. It does not elaborate on the task ID origin or format.

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 the tool queries the status and results of an image generation task. It distinguishes from siblings that generate or list tasks, making it easy to select.

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?

The description mentions that background worker auto-polls, so no manual polling is needed, which implies when to use this tool for checking results. However, it does not explicitly state when not to use it or provide alternatives.

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