create_omnifocus_task
Add a new task to your OmniFocus list directly from this MCP server. Simplify task capture without switching apps.
Instructions
Create a new task in OmniFocus
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Add a new task to your OmniFocus list directly from this MCP server. Simplify task capture without switching apps.
Create a new task in OmniFocus
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits but only says 'Create a new task'. It does not explain what happens with zero parameters, default behavior, 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
While short, the description is under-specified and does not earn its place. It lacks necessary context despite being brief.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, the description is severely incomplete. It does not explain what happens upon execution or how to interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, so the description adds no extra meaning. It fails to clarify how a task can be created without any parameters (e.g., using defaults or a UI), leaving the agent unsure.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb (create), resource (task), and context (OmniFocus), distinguishing it from sibling tools like complete_omnifocus_task.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool over alternatives like create_reminder or create_note. The description does not mention any prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'
If you have feedback or need assistance with the MCP directory API, please join our Discord server