Skip to main content
Glama
someposer
by someposer

activate_task

Reactivate a dropped or completed task in OmniFocus by providing the task ID, enabling users to restore tasks for continued use or management.

Instructions

Activate (un-drop or un-complete) a task in OmniFocus.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe ID of the task to activate

Implementation Reference

  • MCP tool handler for 'activate_task'. Includes input schema via Annotated Field, docstring description, and delegates to omnifocus.activate_task helper. Automatically registered via @mcp.tool decorator.
    @mcp.tool
    def activate_task(task_id: Annotated[str, Field(description="The ID of the task to activate")]) -> dict[str, str]:
        """Activate (un-drop or un-complete) a task in OmniFocus."""
        return omnifocus.activate_task(task_id)
  • Core helper function implementing task activation via JavaScript execution in OmniFocus. Retrieves task by ID, sets task.active = true, formats and returns task details.
    def activate_task(task_id: str) -> dict[str, str]:
        """Activate a task in OmniFocus.
    
        Args:
            task_id: The ID of the task to activate.
    
        Returns:
            A dictionary containing the activated 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.active = true;
            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?

No annotations are provided, so the description carries the full burden. It mentions the action but does not disclose behavioral traits like permissions needed, whether changes are reversible, side effects on related tasks, or error handling. For a mutation tool without annotations, this is a significant gap in transparency.

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 front-loads the purpose with zero waste. It uses parentheses for clarification without redundancy, making it appropriately sized and well-structured.

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 the tool is a mutation with no annotations and no output schema, the description is incomplete. It lacks details on what happens after activation, potential errors, or system behavior, which are crucial for an agent to use it correctly in context with siblings like 'update_task'.

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 'task_id' parameter. The description does not add any meaning beyond what the schema provides, such as format examples or constraints, but the baseline is 3 when schema coverage is high.

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 clearly states the specific action ('Activate') and resource ('a task in OmniFocus'), and distinguishes it from siblings by specifying what activation means ('un-drop or un-complete'), which differentiates it from tools like 'complete_task' or 'drop_task'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by defining activation as reversing drop or completion states, suggesting it should be used on tasks that are dropped or completed. However, it does not explicitly state when not to use it or name alternatives, such as whether it applies to all task states or only specific ones.

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