Skip to main content
Glama

workflowy_complete_node

Mark a WorkFlowy node as completed to track task progress and maintain organized outlines.

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)

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the core logic: rate limiting, client retrieval, API call to complete_node, and error handling. Returns the updated node.
    @mcp.tool(name="workflowy_complete_node", description="Mark a WorkFlowy node as completed")
    async def complete_node(node_id: str) -> WorkFlowyNode:
        """Mark a WorkFlowy node as completed.
    
        Args:
            node_id: The ID of the node to complete
    
        Returns:
            The updated WorkFlowy node
        """
        client = get_client()
    
        if _rate_limiter:
            await _rate_limiter.acquire()
    
        try:
            node = await client.complete_node(node_id)
            if _rate_limiter:
                _rate_limiter.on_success()
            return node
        except Exception as e:
            if _rate_limiter and hasattr(e, "__class__") and e.__class__.__name__ == "RateLimitError":
                _rate_limiter.on_rate_limit(getattr(e, "retry_after", None))
            raise
  • Pydantic BaseModel defining the structure of WorkFlowyNode, used as the return type for the tool. Includes fields like id, name, note, completedAt, children, with validators and properties for compatibility.
    class WorkFlowyNode(BaseModel):
        """Represents a single node in the WorkFlowy outline hierarchy."""
    
        # API fields (what the API actually returns)
        id: str = Field(..., description="Unique identifier for the node")
        name: str | None = Field(
            None, validation_alias=AliasChoices("name", "nm"), description="Text content of the node"
        )
        note: str | None = Field(
            None,
            validation_alias=AliasChoices("note", "no"),
            description="Note content attached to the node",
        )
        priority: int | None = Field(None, description="Sort order")
        data: dict[str, Any] | None = Field(None, description="Node data including layoutMode")
        createdAt: int | None = Field(
            None,
            validation_alias=AliasChoices("createdAt", "created"),
            description="Creation timestamp (Unix timestamp)",
        )
        modifiedAt: int | None = Field(
            None,
            validation_alias=AliasChoices("modifiedAt", "modified"),
            description="Last modification timestamp",
        )
        completedAt: int | None = Field(
            None, description="Completion timestamp (null if not completed)"
        )
    
        # Nested structure fields
        children: list["WorkFlowyNode"] | None = Field(None, alias="ch", description="Child nodes")
        parent_id: str | None = Field(None, alias="parentId", description="Parent node ID")
    
        # Handle 'cp' field for backward compatibility - we'll compute from completedAt
        completed_flag: bool | None = Field(
            None, alias="cp", description="Completion status (for tests)"
        )
    
        @property
        def layoutMode(self) -> str | None:
            """Extract layoutMode from data field."""
            if self.data and isinstance(self.data, dict):
                return self.data.get("layoutMode")
            return None
    
        # Backward compatibility aliases for tests
        @property
        def nm(self) -> str | None:
            """Backward compatibility for name field."""
            return self.name
    
        @property
        def no(self) -> str | None:
            """Backward compatibility for note field."""
            return self.note
    
        @property
        def cp(self) -> bool:
            """Backward compatibility for completed status."""
            # Use completed_flag if it was set (from tests), otherwise check completedAt
            if self.completed_flag is not None:
                return self.completed_flag
            return self.completedAt is not None
    
        @property
        def ch(self) -> list["WorkFlowyNode"] | None:
            """Backward compatibility for children field."""
            return self.children
    
        @property
        def created(self) -> int:
            """Backward compatibility for created timestamp."""
            return self.createdAt or 0
    
        @property
        def modified(self) -> int:
            """Backward compatibility for modified timestamp."""
            return self.modifiedAt or 0
    
        @field_validator("id")
        @classmethod
        def validate_id(cls, v: str) -> str:
            """Ensure ID is non-empty."""
            if not v or not v.strip():
                raise ValueError("Node ID must be non-empty")
            return v
    
        @field_validator("createdAt", "modifiedAt", "completedAt")
        @classmethod
        def validate_timestamp(cls, v: int | None) -> int | None:
            """Ensure timestamps are positive."""
            if v is not None and v <= 0:
                raise ValueError("Timestamp must be positive")
            return v
    
        def model_dump(self, **kwargs: Any) -> dict[str, Any]:
            """Custom serialization to include backward compatibility fields."""
            data: dict[str, Any] = super().model_dump(**kwargs)
    
            # Add backward compatibility fields for tests
            data["nm"] = self.name
            data["no"] = self.note
            data["cp"] = self.cp
            data["ch"] = self.children
            data["created"] = self.createdAt or 0
            data["modified"] = self.modifiedAt or 0
    
            return data
    
        class Config:
            """Pydantic model configuration."""
    
            populate_by_name = True  # Allow both field names and aliases
            json_schema_extra = {
                "example": {
                    "id": "node-123",
                    "name": "Example Node",
                    "note": "This is a note",
                    "priority": 1,
                    "layoutMode": "bullets",
                    "createdAt": 1704067200,
                    "modifiedAt": 1704067200,
                    "completedAt": None,
                    "children": [],
                }
            }
    
    
    # Enable forward references for recursive model
    WorkFlowyNode.model_rebuild()
  • The @mcp.tool decorator that registers the complete_node function as the MCP tool named 'workflowy_complete_node'.
    @mcp.tool(name="workflowy_complete_node", description="Mark a WorkFlowy node as completed")
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.

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/vladzima/workflowy-mcp'

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