Skip to main content
Glama
Sign In
mcp-server-fanqie

mcp-server-fanqie

by fysh1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_manga_progress

Check the download progress of a manga task using its unique task ID to monitor completion status.

Instructions

Query the progress of a manga download task by its task ID (returned from the comic content interface)

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": "get_manga_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID returned from the manga/comic content interface

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'query the progress' without disclosing whether the operation is read-only, idempotent, or what the response format might be. More detail on behavior (e.g., polling semantics) is needed.

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 a single front-loaded sentence with no wasted words. Every part is informative.

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 simple tool with one parameter and no output schema, the description is adequate but could be more complete. It doesn't describe the return value structure, possible statuses, or error cases, which would help an agent interpret results.

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?

The schema covers the parameter with a description that matches the tool's description. The tool description adds context that the task_id comes from the comic content interface, but this adds minimal value. With 100% schema coverage, baseline 3 is appropriate.

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 progress of a manga download task using a task ID. It specifies the source (comic content interface), which distinguishes it from sibling tools that retrieve content or other data.

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 usage when a task ID is available from the comic content interface, but it does not explicitly state when to use this tool versus alternatives like get_content or get_chapter_content. No alternatives or exclusions are mentioned.

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