docflow-mcp

Docflow Delete Category Fields

docflow_delete_category_fields

Delete specified fields from a document category by supplying workspace, category, and field IDs to update the category structure.

Instructions

Delete fields from a category (POST /category/fields/delete).

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>",
      "field_ids": "<field_ids>"
    },
    "name": "docflow_delete_category_fields"
  }
}

Input Schema

Name	Required	Description	Default
`field_ids`	Yes
`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

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Delete' clearly implies a destructive mutation, but the description does not state whether deletion is permanent, whether it affects existing category data, whether permissions are required, or what happens to related field definitions.

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 focused sentence with no filler. The action is front-loaded and the endpoint reference is compact and relevant. It earns its place without unnecessary detail.

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

Completeness2/5

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

For a destructive tool with no annotations and zero schema descriptions, this description is too thin. It lacks usage context, behavioral caveats, and prerequisite guidance. Output schema exists so return values need not be detailed, but the surrounding operational context is still missing.

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%, so the description must compensate, but it only paraphrases 'fields from a category.' The parameter names field_ids, category_id, and workspace_id are somewhat self-explanatory, yet the description does not clarify their relationships, constraints, or how the IDs should be obtained.

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 states the exact action and resource: 'Delete fields from a category.' This unambiguously distinguishes it from sibling tools like delete_category, add_category_fields, or delete_category_samples, so an agent knows precisely which tool to pick.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no mention that field_ids should come from list_category_fields. The description merely restates the operation without giving an agent decision context.

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

Deploy Server