multimodal-mcp

by LinJianKun

Overview Schema Source Related Servers Discussions Admin

Python

Local

mm_query_comic_video

Read-onlyIdempotent

Check the progress of a comic video production task using its job ID and get the final video path once complete.

Instructions

查询漫剧生产任务进度；完成后返回成片路径。

Args: job_id: mm_start_comic_video 返回的任务 ID。

Returns: str: 进度信息或最终视频路径。

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": {
      "job_id": "<job_id>"
    },
    "name": "mm_query_comic_video"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds return behavior (progress vs. final path), but since an output schema exists, this is partially redundant. No contradiction with annotations.

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 clear sections: purpose, Args, and Returns. Every sentence earns its place, and the front-loaded purpose sentence immediately conveys what the tool does. No unnecessary words.

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

Completeness4/5

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

For a simple query tool with one parameter and an output schema, the description adequately covers the operation, input origin, and return type. It could mention explicit alternatives or when not to use, but the context signals (sibling tools) and naming make the specialization clear.

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 0%, but the description compensates by explaining that job_id is the ID returned by mm_start_comic_video. This adds meaningful semantics beyond the schema's bare 'Job Id' field, though more detail about format or constraints could be provided.

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's function: querying comic production task progress and returning the final video path upon completion. The verb '查询' and resource '漫剧生产任务进度' are specific, and the reference to mm_start_comic_video distinguishes it from the generic sibling mm_query_video_task.

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 explains that job_id comes from mm_start_comic_video, providing clear context for when to use this tool (after starting a comic video task). It does not explicitly list alternatives or exclusions, but the context is sufficient for a focused query tool.

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

Deploy Server