docflow-mcp

Docflow Update Category Table

docflow_update_category_table

Update a category's table configuration to change how documents are processed, including renaming or enabling multi-table data collection.

Instructions

Update a table configuration in a category (POST /category/tables/update).

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_id": "<table_id>"
    },
    "name": "docflow_update_category_table"
  }
}

Input Schema

Name	Required	Description
`name`	No
`table_id`	Yes
`category_id`	Yes
`workspace_id`	Yes
`collect_from_multi_table`	No	Whether to collect data from multiple tables on the page.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

C2.1/5.0

Behavior1/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Update', which is already implied by the name, without stating side effects, permissions, reversibility, output format, or any operational implications. This is a significant gap for a mutation tool.

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

Conciseness2/5

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

The description is a single sentence, which is concise, but it is under-specified rather than pragmatic. It includes only the endpoint, offering no additional insight. This is closer to under-specification than effective conciseness.

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

Completeness1/5

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

For a mutation tool with no annotations and low schema coverage, this description is critically incomplete. It does not explain what 'table configuration' means, what fields are updatable, what happens after the update, or any operational context, leaving agents with insufficient information to call it correctly.

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 only 20% (only collect_from_multi_table has a description), and the description itself adds nothing about parameters, their semantics, defaults, or relationships. With such low coverage, the description should compensate but does not, leaving agents to guess about workspace_id, category_id, and table_id.

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 specific verb ('Update') and resource ('a table configuration in a category'), which clearly indicates the action. It is distinguishable from sibling update tools by focusing on 'table configuration', although it does not explicitly name alternatives or contrast with them.

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 guidance is provided on when to use this tool versus other update tools (e.g., docflow_update_category, docflow_update_category_field). There is no mention of prerequisites, specific scenarios, or alternatives, leaving the agent to infer usage from the name and parameters.

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

Deploy Server