docflow-mcp

Docflow Delete Category Tables

docflow_delete_category_tables

Delete specified table configurations from a document category by providing workspace, category ID, and table IDs. Removes unwanted tables to keep category structures accurate.

Instructions

Delete table configurations from a category (POST /category/tables/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>",
      "category_id": "<category_id>",
      "table_ids": "<table_ids>"
    },
    "name": "docflow_delete_category_tables"
  }
}

Input Schema

Name	Required	Description	Default
`table_ids`	Yes
`category_id`	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.9/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 the full burden of behavioral disclosure. It states the destructive action ('Delete') but does not mention irreversibility, cascading effects on associated data, permission requirements, or what happens to dependent configurations. This is a significant gap for a destructive tool.

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, direct sentence with no filler, and the endpoint is useful context. It is concise and front-loaded, though it sacrifices explanatory depth for brevity.

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?

Despite being a simple destructive tool, the description is too thin given the absence of annotations and schema descriptions. An agent cannot determine what valid table_ids look like or whether deleting table configurations triggers side effects. The output schema helps with return values but not invocation semantics.

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

Parameters2/5

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

With 0% schema description coverage, the description must compensate by explaining parameters, but it only says 'from a category', which implies category_id. It does not explain table_ids (e.g., that they are configuration IDs from a list call) or why workspace_id is required, leaving agents to infer from property names alone.

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 identifies the action (delete), the resource (table configurations), and the scope (from a category), and includes the HTTP endpoint. This distinguishes it from siblings like docflow_delete_category, which deletes the category itself, and docflow_delete_files, which deletes files.

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?

There is no guidance on when to use this tool versus alternatives such as docflow_update_category_table (to modify rather than delete) or docflow_list_category_tables (to retrieve IDs). No prerequisites, exclusions, or workflow context are provided; the use case is only implied by 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