create_omnifocus_task

Create tasks in OmniFocus using AI agents. Integrate Claude, Cursor, or Windsurf with macOS task management while keeping all data on your Mac.

Instructions

Create a new task in OmniFocus

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:82-86 (registration)
Tool registration loop where create_omnifocus_task is registered with all other tools. Each tool is registered with an empty schema {} and a stub handler that returns an inspection message.
```
for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
  }));
}
```
server.js:41-41 (registration)
The create_omnifocus_task tool entry in the TOOLS array, defining the tool name and description.
```
["create_omnifocus_task", "Create a new task in OmniFocus"],
```

server.js:1-11 (helper)

File header comments and imports. The comment indicates this is a minimal stub for Glama inspection and the real server is a native macOS binary.

#!/usr/bin/env node
/**
 * Minimal MCP stub for Glama inspection.
 * Lists all Pilot MCP tools so Glama can detect them.
 * The real server is a native macOS binary.
 */
const { McpServer } = require("@modelcontextprotocol/sdk/server/mcp.js");
const { StdioServerTransport } = require("@modelcontextprotocol/sdk/server/stdio.js");
const { z } = require("zod");

const server = new McpServer({ name: "pilot-mcp", version: "2.2.0" });

Tool Definition Quality

B3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Create' implying a write operation, but fails to describe what happens upon invocation (what fields are initialized, return value format, error conditions, or side effects).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no redundant words. However, given the unusual nature of a creation tool accepting zero parameters, additional context would be warranted to explain this constraint.

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

Completeness2/5

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

With no output schema, no annotations, and zero input parameters, the description should clarify what task gets created (default values? blank task?) and what the return value contains. The absence of this explanation leaves a significant gap given the counterintuitive zero-parameter interface.

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?

The input schema contains zero parameters (empty properties object). Per the scoring rubric, zero parameters establishes a baseline score of 4, as there are no parameter semantics to describe beyond the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Create') and resource ('task in OmniFocus'), distinguishing it from sibling 'complete_omnifocus_task' (create vs complete) and from 'create_reminder' (OmniFocus vs Reminders app). However, it lacks specificity about what distinguishes this from other task-creation tools in the broader ecosystem.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'create_reminder' or 'complete_omnifocus_task'. There are no prerequisites, exclusions, or workflow context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Pilot MCP