Skip to main content
Glama
daniel347x

WorkFlowy MCP Server

by daniel347x
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

workflowy_uncomplete_node

Mark a WorkFlowy node as not completed to track incomplete tasks or items in your outline.

Instructions

Mark a WorkFlowy node as not 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. Dates show when Glama detected each change.

  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.3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Mark as not completed' implies a state mutation, it doesn't disclose whether this requires authentication, what happens if the node doesn't exist or isn't completed, whether the change is reversible, or any rate limits. The description provides minimal behavioral context beyond the basic action.

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 that states the core functionality without any wasted words. It's appropriately sized for a simple tool and gets straight to the point. Every word earns its place in conveying the essential action.

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 simplicity (single parameter, no annotations, but has output schema), the description is minimally adequate. The output schema existence means the description doesn't need to explain return values. However, for a state mutation tool with no annotations, the description should provide more behavioral context about what 'marking as not completed' entails in the WorkFlowy system and any constraints.

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 0% description coverage, so the description must compensate. However, it provides no information about the 'node_id' parameter - what format it should be, where to find it, or what constitutes a valid ID. The description adds no parameter semantics beyond what's implied by the tool name, leaving the single required parameter completely undocumented in both schema and description.

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 not completed') and resource ('a WorkFlowy node'), making the purpose immediately understandable. It distinguishes from sibling 'workflowy_complete_node' by specifying the opposite state change. However, it doesn't specify what 'not completed' means in the WorkFlowy context, leaving some ambiguity.

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 when a previously completed node needs to be marked incomplete, but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided about prerequisites (e.g., the node must exist and be currently marked as completed) or when not to use it. The existence of 'workflowy_complete_node' as a sibling suggests a clear alternative, but this isn't mentioned in the description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/daniel347x/workflowy-mcp-fixed'

If you have feedback or need assistance with the MCP directory API, please join our Discord server