Skip to main content
Glama
someposer
by someposer

create_task

Automate task creation in OmniFocus by defining a name and optional note. Streamline task management using MCP OmniFocus server for integration with VS Code, command line, or MCP-compatible clients.

Instructions

Create a new task in OmniFocus with a name and an optional note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the task to create
noteNoThe note for the task, None if no note

Implementation Reference

  • FastMCP tool handler, registration, and schema definition for the 'create_task' tool. Delegates implementation to omnifocus utility.
    @mcp.tool
    def create_task(
        name: Annotated[str, Field(description="The name of the task to create")],
        note: Annotated[str | None, Field(description="The note for the task, None if no note")] = None,
    ) -> dict[str, str]:
        """Create a new task in OmniFocus with a name and an optional note."""
        return omnifocus.create_task(task_name=name, task_note=note)
  • Helper utility that executes JavaScript in OmniFocus to create a new task with name and optional note, then formats and returns task details.
    def create_task(task_name: str, task_note: str | None = None) -> dict[str, str]:
        """Create a new task in OmniFocus.
    
        Args:
            task_name: The name of the task to create.
            task_note: An optional note for the task.
    
        Returns:
            A dictionary containing the created task's details.
        """
        script = Template(
            dedent("""
        ${__common_functions__}
        
        (() => {
            let task = new Task("${task_name}");
            let task_note = ${task_note};
            if (task_note) {
                task.note = task_note;
            }
            return formatTask(task);
        })();
        """)
        )
    
        return evaluate_javascript(
            script.substitute(
                __common_functions__=__common_functions__,
                task_name=task_name,
                task_note=f'"{task_note}"' if task_note else "null",
            )
        )
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 mentions creation with name and note. It lacks critical behavioral details such as required permissions, whether tasks are saved immediately, default settings (e.g., project, context), or error handling, which are essential 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 that directly states the tool's purpose and parameters without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, return values, or error conditions, leaving significant gaps in understanding how to use the tool effectively.

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 both parameters fully. The description adds minimal value by summarizing the parameters but doesn't provide additional context like format constraints or examples beyond what's in the schema.

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 ('Create a new task') and resource ('in OmniFocus'), specifying the required name and optional note. It distinguishes from sibling tools like 'update_task' or 'list_tasks' by focusing on creation, though it doesn't explicitly contrast with them.

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 on when to use this tool versus alternatives like 'update_task' for modifying existing tasks or 'list_tasks' for viewing. The description only states what it does, not when it's appropriate, leaving the agent to infer usage from context.

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