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

query_omnifocus

Retrieve specific tasks, projects, or folders from OmniFocus using flexible filters, field selections, sorting, and limits. Get targeted results without full database dumps.

Instructions

Efficiently query OmniFocus database with filters, fields, sorting, limits, and summaries. Prefer this over dump_database for targeted lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYesType of entity to query. Choose 'tasks' for individual tasks, 'projects' for projects, or 'folders' for folder organization
filtersNoOptional filters to narrow results. ALL filters combine with AND logic (must match all). Within array filters (tags, status) OR logic applies
fieldsNoSpecific fields to return (reduces response size). TASK FIELDS: id, name, note, flagged, taskStatus, dueDate, deferDate, plannedDate, effectiveDueDate, effectiveDeferDate, effectivePlannedDate, completionDate, dropDate, effectiveDropDate, estimatedMinutes, tagNames, tags, projectName, projectId, parentId, childIds, hasChildren, sequential, completedByChildren, inInbox, isRepeating, repetitionRule, modificationDate (or modified), creationDate (or added). PROJECT FIELDS: id, name, status, note, folderName, folderID, sequential, dueDate, deferDate, effectiveDueDate, effectiveDeferDate, completionDate, dropDate, effectiveDropDate, completedByChildren, containsSingletonActions, taskCount, tasks, nextReviewDate, reviewInterval, modificationDate, creationDate. FOLDER FIELDS: id, name, path, parentFolderID, status, projectCount, projects, subfolders. NOTE: Date fields use 'added' and 'modified' in OmniFocus API
limitNoMaximum number of items to return. Useful for large result sets. Default: no limit
sortByNoField to sort by. OPTIONS: name (alphabetical), dueDate (earliest first, null last), deferDate (earliest first, null last), modificationDate (most recent first), creationDate (oldest first), estimatedMinutes (shortest first), taskStatus (groups by status)
sortOrderNoSort order. 'asc' = ascending (A-Z, old-new, small-large), 'desc' = descending (Z-A, new-old, large-small). Default: 'asc'
includeCompletedNoInclude completed and dropped items. Default: false (active items only)
summaryNoReturn only count of matches, not full details. Efficient for statistics. Default: false
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It mentions efficiency but does not explicitly state it is read-only or disclose any side effects or rate limits. The comprehensive schema somewhat compensates, but the description adds minimal 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?

The description is extremely concise, using two sentences to convey the purpose and a usage hint. Every word adds value.

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?

Given the tool's complexity (8 parameters, nested objects) and the lack of an output schema, the description could have mentioned the return format or provided additional context about the output. The schema covers the input well, but the agent lacks guidance on what to expect as a result.

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%, and the schema itself provides very detailed parameter semantics including case sensitivity, AND/OR logic, and date formats. The description only summarizes parameters without adding significant new meaning.

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 the tool queries an OmniFocus database with various features and explicitly distinguishes it from dump_database for targeted lookups. The verb 'query' and resource are well-defined.

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

Usage Guidelines4/5

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

The description gives a clear preference over dump_database for targeted lookups, but does not explicitly list when to avoid or mention other sibling tools like get_flagged_tasks.

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