Skip to main content
Glama

project_update_describe

Preview project update effects without mutation. Inspect planned fields and confirm changes before applying the actual update.

Instructions

Preview what project_update would do without making any changes. Do NOT use to actually update a project — use project_update instead. Returns { description, plannedChanges } showing the fields that would be patched. 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
idYesPersistent project ID. Get from project_list or project_get.
nameNoNew project name. Must be non-empty if supplied.
noteNoPlain-text note. Pass null to clear.
statusNoProject status. Use project_complete or project_drop to close a project. Accepts: 'paused' → on-hold.
tagIdsNoFull-replacement tag list. Replaces all existing tags.
dry_runNoWhen true, validates input and returns a preview envelope with meta.dryRun = true; no adapter call is made and no mutation occurs.
dueDateNoISO-8601 due date with UTC offset. Pass null to clear.
flaggedNoFlag or unflag the project.
noteHtmlNoHTML note. Pass null to clear. Prefer note for plain-text edits.
deferDateNoISO-8601 defer date with UTC offset. Pass null to clear.
dueDateFloatingNoWhen true, the due time is floating (follows the user across time zones).
idempotency_keyNoIdempotency key for retry-safe updates. Identical subsequent calls within the TTL window replay the original envelope with meta.idempotentReplay = true instead of re-applying the patch.
estimatedMinutesNoEstimated total duration in minutes. Pass null to clear.
deferDateFloatingNoWhen true, the defer time is floating (follows the user across time zones).
expectedModifiedAtNoOptimistic-concurrency guard: ISO-8601 timestamp from a recent project_get. If the project's current modifiedAt differs, the call fails with OF_CONFLICT and no update is performed. Omit to skip the check.
reviewIntervalDaysNoReview interval in days. Pass null to clear.
completionCriterionNoHow the project's tasks are completed. Accepts: 'in-order' → sequential, 'in order' → sequential, 'any-order' → parallel, 'any order' → parallel.
Behavior5/5

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

The description states 'No side effects: read-only by contract — never mutates OmniFocus.' It also describes the return shape ({ description, plannedChanges }) and that it is a dry-run companion. With no annotations provided, this fully discloses the behavioral traits.

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 concise with three sentences, no wasted words. The main purpose is front-loaded in the first sentence, and subsequent sentences add necessary context without redundancy.

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?

For a preview tool with no output schema, the description describes the return shape explicitly. It also mentions the dry-run concept and the relationship to project_update, providing all needed context for an agent to use it correctly.

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 documents all 17 parameters. The description does not add per-parameter meaning beyond saying to pass the same args as project_update. Baseline is 3, and no additional value is added for individual parameters.

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 it previews what project_update would do without changes, distinguishing it from the actual update tool. It specifies the verb 'preview' and the resource 'project update', and contrasts with the sibling tool project_update.

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?

The description explicitly says 'Do NOT use to actually update a project — use project_update instead.' It also provides a usage pattern: pass args to inspect plannedChanges then call the write tool, giving 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/torsday/omnifocus-mcp'

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