Skip to main content
Glama

task_create_describe

Preview a new task in OmniFocus without creating it. Inspect planned changes before calling the actual create tool.

Instructions

Preview what task_create would do without making any changes. Do NOT use to actually create a task — use task_create instead. Returns { description, plannedChanges } describing the task that would be created. No side effects: read-only by contract — never mutates OmniFocus. Example: dry-run companion — pass the same args you would to the write tool, inspect plannedChanges, then call the write tool once approved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTask name. Required, must be non-empty.
noteNoPlain-text note.
tagIdsNoTag IDs to apply.
dueDateNoDue date as ISO-8601 with offset.
flaggedNoFlag the task.
deferDateNoDefer date as ISO-8601 with offset.
projectIdNoProject to add the task to. Omit for inbox or subtask.
sequentialNoIf true, subtasks must be completed in order.
parentTaskIdNoParent task ID for a subtask. Omit for inbox or project task.
dueDateFloatingNoWhen true, the due time follows the user across time zones (floating) rather than being pinned to a fixed UTC instant. Use for recurring daily tasks where '9 AM' should mean 9 AM wherever the user is. Default: false (fixed-offset).
idempotency_keyNoIdempotency key for retry-safe creates. Identical subsequent calls within the TTL window replay the original envelope with meta.idempotentReplay = true instead of creating a duplicate task.
estimatedMinutesNoEstimated duration in minutes.
deferDateFloatingNoWhen true, the defer time is floating (follows the user across time zones).
completedByChildrenNoComplete when all subtasks complete.
Behavior5/5

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

Explicitly states 'No side effects: read-only by contract — never mutates OmniFocus.' This goes beyond the lack of annotations by clarifying the tool's safety and describing the return format (description and plannedChanges).

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?

Three concise sentences with no redundancy. Front-loaded with core purpose, then safety note, then usage example. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the lack of output schema, the description clearly states what it returns and its role as a dry-run. It covers all essential aspects: purpose, safety, usage pattern, and relation to sibling tool.

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 description does not need to repeat parameter details. It mentions the tool accepts the same arguments as task_create, which adds context but doesn't elaborate beyond the schema.

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?

Explicitly states it previews task_create without changes, distinguishes from the sibling tool by warning to use task_create for actual creation. Verb 'Preview' and resource 'task_create' are specific and clear.

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?

Directly says when to use (as a dry-run) and when not to (use task_create for actual creation). Provides workflow: pass same args, inspect plannedChanges, then call the write tool. Offers clear alternative.

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

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