docflow-mcp

Docflow Delete Review Task

docflow_delete_review_task

Delete review tasks from a Docflow workspace by supplying their task IDs, removing unwanted or obsolete items from compliance workflows.

Instructions

Delete review tasks (POST /review/task/delete).

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>",
      "task_ids": "<task_ids>"
    },
    "name": "docflow_delete_review_task"
  }
}

Input Schema

Name	Required	Description	Default
`task_ids`	Yes
`workspace_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely says 'Delete review tasks', which implies destructiveness but does not state whether deletion is permanent, reversible, or scoped to the given workspace_id. No information about side effects, permissions, or errors is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no redundant words. It front-loads the action and appends the endpoint, which is useful but not essential. It is well-structured and concise, though under-specified.

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

Completeness2/5

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

Given the tool's simplicity, the description is minimal but lacks essential context such as the relationship between workspace_id and task_ids, what a review task is, and the expected outcome. The presence of an output schema covers return values, but behavioral and usage gaps remain significant for an AI agent to invoke this tool correctly without additional investigation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain what task_ids or workspace_id mean, how they relate, or what formats are expected. The agent must rely solely on the parameter names, which are ambiguous without additional context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Delete review tasks'. It also adds the API endpoint '(POST /review/task/delete)', which adds specificity. However, it mostly restates the tool name and does not distinguish itself from other review-task siblings beyond the obvious 'delete' action, so it falls short of a 5.

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?

The description provides no guidance on when to use this tool versus alternatives such as docflow_retry_review_task or docflow_get_review_result. There is no mention of prerequisites, context, or when not to use it, leaving the agent to infer usage solely from the name.

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

Deploy Server