docflow-mcp

Docflow Create Category

docflow_create_category

Create a document category by defining custom fields and uploading a sample file, enabling automatic classification of similar documents.

Instructions

Create a file category with field configuration and a sample file.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Category name (e.g. "增值税发票", "酒店水单").
`fields`	Yes	Field definitions. Format: [{"name": "发票金额", "description": "价税合计"}]
`workspace_id`	Yes	Target workspace.
`extract_model`	No	"llm" for text-heavy docs, "vlm" for scanned/layout-complex docs.	llm
`category_prompt`	No	Optional classification hint (max 500 chars).
`sample_file_path`	Yes	Local path to a sample file (PDF/image). Required for classification.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

B3.1/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, but it only states the action without any side effects or behavioral context. It does not mention persistence, conflict behavior on duplicate category names, what happens to the sample file, or that extract_model defaults to 'llm'.

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 filler. It communicates the essential create action and the two notable creation components efficiently.

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 schema is rich enough to make the tool invocable, and the output schema exists so return values need not be explained. However, the description lacks broader workflow context, side-effect expectations, and prerequsite awareness, leaving an agent to infer the surrounding setup process.

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 input schema already covers 100% of parameters with descriptions and default values, so the baseline is 3. The description adds only high-level mention of field configuration and a sample file, while the schema provides the concrete array format and extract_model guidance.

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 uses a specific verb ('Create') and resource ('file category') and highlights the two key creation payloads ('field configuration' and 'sample file'). It is clear enough to distinguish from sibling list/update/delete category tools, though it does not explicitly contrast with docflow_amend_category or docflow_update_category.

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 gives no guidance on when this should be used instead of related tools like docflow_amend_category or docflow_update_category. It also omits prerequisites such as the workspace needing to exist or that this is likely an initial-setup step before extraction/review tools.

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

Deploy Server