docflow-mcp

Docflow List Category Fields

docflow_list_category_fields

List all fields configured in a category to retrieve field_ids needed for building review rules with referenced_fields. Returns field details like name and configuration.

Instructions

List all fields configured in a category (GET /category/fields/list).

Returns field_id, name, description, and configuration for each field. Use this to get field_ids needed when building review rules with referenced_fields.

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_fields"
  }
}

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

A4.1/5.0

Behavior4/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. It clearly signals a read-only operation with 'List' and 'GET', and it transparently describes the return contents: field_id, name, description, and configuration. It does not mention pagination or permissions, but for a list operation the behavioral profile is largely clear.

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?

Three sentences with no filler: action, return summary, and usage guidance. The most important information is front-loaded, and every sentence earns its place.

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

Completeness4/5

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

Given the tool's simplicity, two parameters, and the presence of an output schema, the description is largely complete. It provides the endpoint, return fields, and a practical use case. The main missing piece is workspace_id semantics, but that is already captured under parameter 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?

Schema description coverage is 0%, and the description does little to explain the two required parameters. While category_id is implied by 'in a category', workspace_id is not described at all, and no format, source, or relationship guidance is given. The description should compensate for the bare schema but does not.

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 and resource: 'List all fields configured in a category.' It also distinguishes this from siblings like docflow_list_categories and docflow_list_category_tables by naming the exact resource type and including the endpoint. An agent can immediately tell what this tool does and what it is not for.

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 provides a concrete use case: 'Use this to get field_ids needed when building review rules with referenced_fields.' This gives clear context for when to invoke the tool, though it does not explicitly state when not to use it or name alternatives beyond the implied sibling set.

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

Deploy Server