docflow-mcp

Docflow List Category Samples

docflow_list_category_samples

Retrieve all sample files for a category by providing workspace and category IDs. Get sample IDs, file names, and upload times for review or management.

Instructions

List all sample files configured for a category (GET /category/sample/list). Returns sample_id, file name, and upload time for each sample.

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

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.7/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavior disclosure. It communicates a read-only list operation ('GET /category/sample/list') and specifies the response contents (sample_id, file name, upload time), but it does not mention pagination, auth, or other operational edge cases.

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?

Two succinct sentences: the first states the operation and endpoint, the second describes the returned fields. Every sentence is useful and there is no filler or redundant schema repetition.

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?

The output schema covers return structure, so the description does not need to re-enumerate it. The description gives the endpoint, scope ('for a category'), and response gist, which is adequate for a simple list tool; only minor details like pagination or authorization are omitted.

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 for the undocumented parameters. It mentions 'category' only indirectly and never explains workspace_id or category_id semantics beyond what the parameter names already suggest. The description adds no meaningful parameter-level information.

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 sample files configured for a category'. It also includes the HTTP endpoint and enumerates the returned fields, making the tool's function unambiguous and differentiating it from sibling tools like docflow_list_categories or docflow_list_category_tables.

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

Usage Guidelines3/5

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

The description implies usage: call this when you need sample files for an existing category. However, it does not explicitly contrast with sibling list tools, nor does it state when not to use it or any prerequisites beyond the required parameters.

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

Deploy Server