Skip to main content
Glama

task_batch_defer_smart

Defers multiple OmniFocus tasks with individual smart intents (e.g., next work day, next weekday) in a single batch. Returns per-entry success or failure without aborting the entire operation.

Instructions

Batch variant of task_defer_smart: accepts an array of { taskId, intent } and resolves each intent independently. Same intent grammar as task_defer_smart. Do NOT use this for a single task — prefer task_defer_smart for one entry. Returns { results: [{ taskId, ok: true, resolvedDeferDate, reason } | { taskId, ok: false, error }] } — per-entry failures surface inline so one malformed entry does not abort the others. Side effects: writes the resolved deferDate to each successful task; dry_run skips writes. Triggers a sync when any entry succeeds. Example: task_batch_defer_smart({ entries: [{ taskId: '...', intent: { kind: 'next-work-day' } }] })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoWhen true, resolves every intent but does NOT write to OmniFocus. Useful for previewing the batch's resolved dates before committing.
entriesYesArray of { taskId, intent } pairs. Per-entry failures surface in the results array; one bad entry does not abort siblings.
idempotency_keyNoIdempotency key. Identical subsequent calls within the TTL window replay the original results envelope with meta.idempotentReplay = true.
Behavior5/5

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

Discloses side effects: writes deferDate, dry_run skips writes, triggers sync on success, per-entry failures do not abort others. With no annotations, description fully covers behavioral expectations.

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?

Concise two sentences plus example. Front-loaded: declares batch variant, array input, independent resolution. Usage guidance, return format, side effects, and example are succinctly included.

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?

Describes return format, error handling, side effects, and dry run. Lacks explicit mention of idempotency key behavior, but schema covers it. Adequate given complexity and no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds meaning for 'entries' (per-entry failures inline) and 'dry_run'. Does not mention 'idempotency_key', but schema already describes it.

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 identifies as batch variant of task_defer_smart with specific verb 'accepts an array of { taskId, intent } and resolves each intent independently'. Distinguishes from sibling task_defer_smart.

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 states when NOT to use ('Do NOT use this for a single task — prefer task_defer_smart') and explains when to use (batch of multiple tasks). Covers triggers and dry run behavior.

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