docflow-mcp

Docflow List Category Tables

docflow_list_category_tables

List all table configurations in a category to retrieve table IDs, names, and fields, enabling field addition and review rule setup.

Instructions

List all table configurations in a category (GET /category/tables/list).

Returns table_id, name, and fields for each table. Use this to get table_id before adding table fields or building review rules.

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": "docflow_list_category_tables"
  }
}

Input Schema

Name	Required	Description	Default
`category_id`	Yes
`workspace_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only operation via 'List' and the GET endpoint, and mentions it 'Returns' data. However, it does not explicitly state that it has no side effects or require any permissions, and does not disclose any limitations like pagination. For a simple list operation, this is adequate but not rich.

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 sentences: the first states the operation and endpoint, the second states the return and use case. It is front-loaded, has no filler, and every sentence adds value. Highly concise.

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?

For a simple list tool with an output schema, the description covers purpose, return fields, and a common use case. However, it omits any explanation of the parameters, which are essential for correct invocation. This gap makes it incomplete for an agent that needs to know what to pass for workspace_id and category_id.

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 the two required parameters (workspace_id, category_id). It mentions 'category' but does not clarify what the IDs refer to or their format. Since coverage is low, the description must compensate, and it fails to do so, leaving the agent guessing about parameter meaning.

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 'List' and resource 'table configurations in a category', includes the endpoint (GET /category/tables/list), and states the return fields (table_id, name, fields). It clearly differentiates from sibling tools like docflow_list_category_fields (which lists fields) and docflow_add_category_table (which adds), so an agent can select it correctly.

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?

The description explicitly states when to use it: 'Use this to get table_id before adding table fields or building review rules.' This provides a clear context and purpose. It does not mention when not to use or alternatives, but the guidance is specific enough for the primary use case.

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

Deploy Server