Skip to main content
Glama
phd-peter
by phd-peter

add_omnifocus_task

Create a new OmniFocus task with due dates, flags, tags, and project assignment while automatically checking for existing tasks to avoid duplicates.

Instructions

Create a NEW task in OmniFocus. Search first when a matching task may already exist; move/edit existing tasks instead of duplicating them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the task
noteNoAdditional notes for the task
dueDateNoThe due date of the task in ISO format (YYYY-MM-DD or full ISO date)
deferDateNoThe defer date of the task in ISO format (YYYY-MM-DD or full ISO date)
plannedDateNoThe planned date of the task in ISO format (YYYY-MM-DD or full ISO date)
flaggedNoWhether the task is flagged or not
estimatedMinutesNoEstimated time to complete the task, in minutes
tagsNoTags to assign to the task
projectNameNoThe name of the project to add the task to (will add to inbox if not specified)
parentTaskIdNoThe ID of the parent task to create this task as a subtask
parentTaskNameNoThe name of the parent task to create this task as a subtask (alternative to parentTaskId)
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'create' but lacks details on side effects, auth requirements, error handling, or idempotency. Minimal disclosure 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?

Two sentences, no waste, front-loaded with the core purpose. Every sentence earns its place.

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?

For 11 parameters and no output schema, description lacks return value details and behavior for optional fields. Adequate but not complete; e.g., unclear what happens if projectName is invalid.

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 baseline is 3. Description does not add meaning beyond schema; it merely restates parameter purposes implicitly.

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?

Description clearly states 'Create a NEW task in OmniFocus' with a specific verb and resource. It distinguishes from sibling tools like edit_item and move_task by emphasizing creation over duplication.

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

Usage Guidelines5/5

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

Explicitly advises to search first and edit existing tasks instead of duplicating, providing clear when-to-use and when-not-to-use guidance.

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/phd-peter/codex-omnifocus-mcp'

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