docflow-mcp

Docflow Update Workspace

docflow_update_workspace

Update workspace settings to change its name, description, privacy scope, or webhook callback URL for processing notifications.

Instructions

Update workspace settings (POST /workspace/update).

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

Input Schema

Name	Required	Description
`name`	No	New display name.
`auth_scope`	No	0=private (self only), 1=public (enterprise members).
`description`	No	New description.
`callback_url`	No	Webhook URL for processing completion notifications.
`workspace_id`	Yes	Workspace to update.

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 bears the full burden but merely restates the action and HTTP method. It does not disclose side effects, whether unspecified fields are preserved or reset, permission requirements, or the meaning of passing null for optional fields. For a mutation tool, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler and places the core action first, followed by the endpoint in parentheses. It is appropriately terse and scannable, though it is minimal enough that the conciseness borderlines on under-specification.

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?

The tool has five parameters, an output schema, and no annotations, but the description only states the action and endpoint. Missing are usage context, behavioral expectations, and clarification of null semantics for optional fields, leaving an agent to guess at important invocation details despite the rich schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for all five parameters, including workspace_id, name, auth_scope, description, and callback_url. The description itself adds no parameter-specific meaning beyond the generic word 'settings', so the schema legitimately carries the semantic load.

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 a specific verb ('Update') and resource ('workspace settings'), making the tool's function unmistakable. The word 'workspace' distinguishes it from the many sibling tools targeting categories, files, and review rules, and 'update' separates it from get/delete/list workspace operations.

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?

No guidance is given on when to use this tool versus alternatives such as docflow_get_or_create_workspace, docflow_get_workspace, or docflow_retry_files. The description only states the action; there is no mention of preconditions, exclusions, or fallback tools, leaving usage entirely to inference.

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

Deploy Server