docflow-mcp

Docflow Add Category Table

docflow_add_category_table

Add a table field group to a category to extract structured table data such as invoice line items or hotel charges.

Instructions

Add a table field group to a category (POST /category/tables/add).

Use for extracting structured table data (e.g. invoice line items, hotel charges).

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>",
      "name": "<name>",
      "fields": "<fields>"
    },
    "name": "docflow_add_category_table"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Table name (e.g. "货物明细", "消费明细").
`fields`	Yes	Column definitions. Format: [{"name": "列名", "description": "描述"}]
`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

A3.6/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 that the tool adds a table field group, but it does not mention whether the operation is destructive, whether it requires special permissions, whether it is idempotent, or what effect it has on existing category data.

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 two crisp sentences: the first states the operation and endpoint, the second gives a concrete usage context. There is no filler or repeated information.

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 description plus schema provides enough to attempt the call: it names the resource, gives an example, and the schema documents required parameters and the fields format. However, behavioral details such as mutation effects and permission expectations are missing, and two parameters are undocumented in both the schema and description.

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?

Schema description coverage is only 50%, and the description does not compensate for the missing parameter details. It adds no meaning to workspace_id or category_id beyond their names, and it does not explain how the examples like 'invoice line items' map to the fields array structure beyond what the schema already says.

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 uses a specific verb plus resource: 'Add a table field group to a category.' It also includes the endpoint, which makes the operation unambiguous and differentiates it from sibling tools like docflow_add_category_fields or docflow_update_category_table.

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

Usage Guidelines4/5

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

It gives a clear use case: 'Use for extracting structured table data (e.g. invoice line items, hotel charges).' This tells the agent when the tool is appropriate, though it does not explicitly state when not to use it or name a specific alternative.

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

Deploy Server