Skip to main content
Glama

project_create_describe

Preview project creation in OmniFocus without side effects. Inspect planned changes before committing with the write tool.

Instructions

Preview what project_create would do without making any changes. Do NOT use to actually create a project — use project_create instead. Returns { description, plannedChanges } describing the project 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
nameYesProject name. Required, must be non-empty.
noteNoPlain-text note for the project.
statusNoInitial project status. Default: active. Accepts: 'paused' → on-hold.
tagIdsNoTag IDs to apply to the project.
dueDateNoDue date as ISO-8601 with UTC offset.
flaggedNoFlag the project.
folderIdNoFolder ID to place the project in. Omit for root.
deferDateNoDefer date as ISO-8601 with UTC offset.
dueDateFloatingNoWhen true, the due time is floating (follows the user across time zones).
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 project.
estimatedMinutesNoEstimated total duration in minutes.
deferDateFloatingNoWhen true, the defer time is floating (follows the user across time zones).
reviewIntervalDaysNoReview interval in days. Omit to use OmniFocus default.
completionCriterionNoHow the project's tasks are completed: parallel (any order), sequential (in order), or singleActions. Accepts: 'in-order' → sequential, 'in order' → sequential, 'any-order' → parallel, 'any order' → parallel.
Behavior4/5

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

Discloses no side effects, read-only by contract, never mutates OmniFocus. Describes return value structure. No annotations provided, but description adds sufficient behavioral context.

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 plus an example, front-loaded with purpose, no wasted words. Efficient and clear.

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

Completeness4/5

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

With 14 parameters and no output schema, description explains return value and no-side-effect guarantee. Could elaborate on plannedChanges contents, but sufficient for typical use.

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 coverage is 100% with parameter descriptions. Description adds minimal extra meaning beyond noting to pass same args as write tool. Baseline 3 is appropriate.

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?

Clearly states it previews project creation without changes, uses specific verb 'preview' and resource 'project_create'. Distinguishes from sibling 'project_create'.

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 warns against using for actual creation, directs to 'project_create' instead. Provides workflow: dry-run companion, inspect plannedChanges, then call write tool.

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