docflow-mcp

Docflow Run Review

docflow_run_review

Submit document review tasks and wait for compliance results. Specify workspace, review rules, and extraction task IDs to run automated compliance reviews.

Instructions

Submit a review task and wait for results.

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": {
      "workspace_id": "<workspace_id>",
      "repo_id": "<repo_id>",
      "task_ids": "<task_ids>"
    },
    "name": "docflow_run_review"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Display name for this review task.	审核任务
`repo_id`	Yes	Review rule repository ID (from docflow_setup_review_rules).
`timeout`	No	Max seconds to wait (default 300).
`task_ids`	Yes	Extraction task IDs to review (task_id from docflow_upload_and_extract).
`workspace_id`	Yes	Target workspace.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the tool blocks by submitting and waiting for results, which is reinforced by the timeout parameter. However, it does not state what happens on timeout, whether the review task persists for later retrieval, or what side effects occur.

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?

A single front-loaded sentence with no wasted words. The core verb, resource, and blocking behavior are all expressed immediately and clearly.

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 rich input schema and presence of an output schema reduce the burden on the description. Still, the description does not explain the surrounding workflow, timeout behavior beyond the schema default, or when to prefer docflow_get_review_result or docflow_retry_review_task. It is minimally adequate but not fully complete.

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 description coverage is 100%, and each parameter already has meaningful provenance descriptions such as 'from docflow_setup_review_rules' and 'from docflow_upload_and_extract.' The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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?

States a specific action ('Submit') and resource ('review task') and adds 'wait for results,' which distinguishes it from related siblings like docflow_get_review_result or docflow_retry_review_task. The title alone would not convey the blocking nature, but the description does.

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

Usage Guidelines2/5

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

No when-to-use guidance is provided: no mention of prerequisites, exclusions, or alternatives such as docflow_get_review_result or docflow_retry_review_task. The only sequencing hints live in parameter descriptions, not in the tool description itself.

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

Deploy Server