Skip to main content
Glama
daniel347x

WorkFlowy MCP Server

by daniel347x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

workflowy_complete_node

Mark a WorkFlowy node as completed to track task progress and maintain organized outlines through the WorkFlowy MCP Server.

Instructions

Mark a WorkFlowy node as completed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
chNoChild nodes
cpNoCompletion status (for tests)
idYesUnique identifier for the node
dataNoNode data including layoutMode
nameNoText content of the node
noteNoNote content attached to the node
parentIdNoParent node ID
priorityNoSort order
createdAtNoCreation timestamp (Unix timestamp)
modifiedAtNoLast modification timestamp
completedAtNoCompletion timestamp (null if not completed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv1.0.0
    • addedOutput schema / description
      Added value: +"Represents a single node in the WorkFlowy outline hierarchy."
    • addedOutput schema / example
      Added value: +{
+  "children": [],
+  "completedAt": null,
+  "createdAt": 1704067200,
+  "id": "node-123",
+  "layoutMode": "bullets",
+  "modifiedAt": 1704067200,
+  "name": "Example Node",
+  "note": "This is a note",
+  "priority": 1
+}
    • addedOutput schema / properties / ch
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/WorkFlowyNode"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Child nodes"
+}
    • addedOutput schema / properties / completedAt
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Completion timestamp (null if not completed)"
+}
    • addedOutput schema / properties / cp
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Completion status (for tests)"
+}
    • addedOutput schema / properties / createdAt
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Creation timestamp (Unix timestamp)"
+}
    • addedOutput schema / properties / data
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Node data including layoutMode"
+}
    • addedOutput schema / properties / id
      Added value: +{
+  "description": "Unique identifier for the node",
+  "type": "string"
+}
    • addedOutput schema / properties / modifiedAt
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Last modification timestamp"
+}
    • addedOutput schema / properties / name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Text content of the node"
+}
    • addedOutput schema / properties / note
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Note content attached to the node"
+}
    • addedOutput schema / properties / parentId
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Parent node ID"
+}
    • addedOutput schema / properties / priority
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Sort order"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "$ref": "#/$defs/WorkFlowyNode"
-}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "id"
+]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  2. First observed

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. It states the action ('Mark as completed') which implies a mutation, but doesn't describe side effects (e.g., whether this affects parent/child nodes, triggers notifications, or changes visibility), permissions required, error conditions, or rate limits. This leaves significant gaps for a mutation tool.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and appropriate for its simplicity.

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?

Given the tool's moderate complexity (a mutation with one parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and low schema coverage, it lacks crucial behavioral details like side effects or error handling, making it incomplete for safe operation.

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 schema description coverage is 0%, so the description must compensate, but it adds no parameter information beyond what's implied by the tool name. It doesn't explain what 'node_id' represents, its format, or how to obtain it. However, with only one parameter and an output schema present, the baseline is 3 as the schema provides structure, but the description fails to add meaningful semantic context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Mark as completed') and resource ('a WorkFlowy node'), making the purpose immediately understandable. However, it doesn't differentiate from its sibling 'workflowy_uncomplete_node' which would be the inverse operation, nor does it specify what 'completed' means in the WorkFlowy context (e.g., visual strikethrough, status change).

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 provided about when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the node must exist), when not to use it (e.g., on already completed nodes), or how it relates to siblings like 'workflowy_update_node' (which might also modify completion status). The agent must infer usage from the name alone.

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

Deploy Server

Other Tools