Skip to main content
Glama
someposer
by someposer

complete_task

Mark a task as completed in OmniFocus by specifying its unique task ID, enabling efficient task management and progress tracking within the MCP OmniFocus automation framework.

Instructions

Complete a task in OmniFocus.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe ID of the task to complete

Implementation Reference

  • MCP tool handler for 'complete_task', decorated with @mcp.tool for registration, defines input schema via Annotated, and delegates to omnifocus helper.
    @mcp.tool
    def complete_task(task_id: Annotated[str, Field(description="The ID of the task to complete")]) -> dict[str, str]:
        """Complete a task in OmniFocus."""
        return omnifocus.complete_task(task_id)
  • Core implementation of complete_task using JavaScript evaluation to call task.markComplete() in OmniFocus.
    def complete_task(task_id: str) -> dict[str, str]:
        """Complete a task in OmniFocus.
    
        Args:
            task_id: The ID of the task to complete.
    
        Returns:
            A dictionary containing the completed task's details.
        """
        script = Template(
            dedent("""
        ${__common_functions__}
        
        (() => {
            let task = Task.byIdentifier("${task_id}");
            if (!task) {
                throw "Could not find task: " + task_id.toString();
            }
            
            task.markComplete();
            return formatTask(task);
        })();
        """)
        )
    
        return evaluate_javascript(script.substitute(__common_functions__=__common_functions__, task_id=task_id))
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether completion is reversible, if it affects task dependencies, requires specific permissions, or what the response looks like, leaving 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 waste, front-loading the core action and resource. It's appropriately sized for a simple tool, earning its place without unnecessary elaboration.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral impact (e.g., what 'complete' entails), error handling, or return values, which are crucial for an agent to use it correctly in context with siblings.

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?

Schema description coverage is 100%, so the schema already documents the single parameter 'task_id'. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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 ('Complete') and resource ('a task in OmniFocus'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'drop_task' which might also mark tasks as done, missing explicit differentiation.

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 like 'drop_task' or 'update_task' for marking completion. The description lacks context about prerequisites (e.g., task must exist, be active) or exclusions, offering minimal usage direction.

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

Related 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/someposer/mcp-omnifocus'

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