Skip to main content
Glama
mdoel
by mdoel

get_all_tasks

Retrieve all tasks from OmniFocus, including completed items, to provide a comprehensive view of task history and status.

Instructions

Call this tool to get a list of all tasks from OmniFocus, including completed ones. Use it when the user explicitly asks for 'all tasks' or 'completed tasks'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler function implementing the core logic for retrieving all tasks from OmniFocus by executing a JXA script via osascript.
    async getAllTasks(filters: TaskFilters = {}): Promise<OmniFocusTask[]> {
      console.error('[DEBUG] getAllTasks called with filters:', JSON.stringify(filters));
      const jxaScript = buildJxaScriptForTasks(false);
      const output = this.executeScript(jxaScript);
      try {
        const tasks = JSON.parse(output);
        return tasks;
      } catch (e) {
        console.error('[DEBUG] Failed to parse OmniFocus JXA output:', output);
        throw new Error('Failed to parse OmniFocus output as JSON');
      }
    }
  • MCP tool dispatch handler that invokes the OmniFocusClient.getAllTasks() method when the 'get_all_tasks' tool is called.
    case 'get_all_tasks':
      result = await this.client.getAllTasks();
      break;
  • src/server.ts:51-55 (registration)
    Registration of the 'get_all_tasks' tool in the MCP listTools response, including name, description, and input schema.
    {
      name: 'get_all_tasks',
      description: "Call this tool to get a list of all tasks from OmniFocus, including completed ones. Use it when the user explicitly asks for 'all tasks' or 'completed tasks'.",
      inputSchema: { type: 'object', properties: {} }
    },
  • Type definition for OmniFocusTask, which structures the output returned by the get_all_tasks tool.
    export interface OmniFocusTask {
      id: string;
      name: string;
      note: string;
      completed: boolean;
      completionDate?: string | null;
      creationDate: string;
      modificationDate: string;
      dueDate?: string | null;
      deferDate?: string | null;
      estimatedMinutes?: number | null;
      flagged: boolean;
      repetitionRule?: string | null;
      sequential: boolean;
      project?: {
        id: string;
        name: string;
      } | null;
      context?: {
        id: string;
        name: string;
      } | null;
      containingProject?: {
        id: string;
        name: string;
      } | null;
    }
  • Helper function that generates the JavaScript for Automation (JXA) script used by getAllTasks to query all tasks from OmniFocus.
    export function buildJxaScriptForTasks(activeOnly: boolean): string {
      return `
        (() => {
          const app = Application('OmniFocus');
          app.includeStandardAdditions = true;
          const ofDoc = app.defaultDocument;
          function safe(obj, method) {
            try { return obj && typeof obj[method] === 'function' ? obj[method]() : null; } catch { return null; }
          }
          function getContext(task) {
            const ctx = safe(task, 'context');
            return ctx ? { id: safe(ctx, 'id'), name: safe(ctx, 'name') } : null;
          }
          function getProject(task) {
            const proj = safe(task, 'containingProject');
            return proj ? { id: safe(proj, 'id'), name: safe(proj, 'name') } : null;
          }
          function isInTemplatesFolder(project) {
            let folder = safe(project, 'folder');
            while (folder) {
              if (safe(folder, 'name') === 'Templates') return true;
              folder = safe(folder, 'parentFolder');
            }
            return false;
          }
          function isExcludedTask(task) {
            const name = safe(task, 'name') || '';
            const note = safe(task, 'note') || '';
            if (name.includes('«') || name.includes('»') || note.includes('«') || note.includes('»')) return true;
            if (name.includes('⚙️') || note.includes('⚙️')) return true;
            const proj = safe(task, 'containingProject');
            if (!proj) return false;
            return isInTemplatesFolder(proj);
          }
          function getTaskData(task) {
            return {
              id: safe(task, 'id'),
              name: safe(task, 'name'),
              note: safe(task, 'note'),
              completed: safe(task, 'completed'),
              status: safe(task, 'status'),
              completionDate: safe(task, 'completionDate') ? safe(task, 'completionDate').toISOString() : null,
              creationDate: safe(task, 'creationDate') ? safe(task, 'creationDate').toISOString() : null,
              modificationDate: safe(task, 'modificationDate') ? safe(task, 'modificationDate').toISOString() : null,
              dueDate: safe(task, 'dueDate') ? safe(task, 'dueDate').toISOString() : null,
              deferDate: safe(task, 'deferDate') ? safe(task, 'deferDate').toISOString() : null,
              estimatedMinutes: safe(task, 'estimatedMinutes'),
              flagged: safe(task, 'flagged'),
              repetitionRule: safe(task, 'repetitionRule'),
              sequential: safe(task, 'sequential'),
              project: safe(task, 'project'),
              context: getContext(task),
              containingProject: getProject(task)
            };
          }
          const allTasks = Array.from(ofDoc.flattenedTasks());
          const filteredTasks = allTasks.filter(task => {
            if (isExcludedTask(task)) return false;
            const statusObj = safe(task, 'status') ? task.status() : null;
            const statusName = statusObj ? safe(statusObj, 'name') : '';
            if (${activeOnly ? 'true' : 'false'}) {
              // Exclude completed or dropped tasks
              return !task.completed() && !/dropped/i.test(statusName);
            }
            return true;
          });
          const result = filteredTasks.map(getTaskData);
          return JSON.stringify(result);
        })();
      `;
    }
Behavior3/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 the tool retrieves a list of all tasks, implying a read-only operation, but lacks details on potential limitations like rate limits, authentication needs, or how the data is structured in the response. It adds basic context but misses richer 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 front-loaded and concise, consisting of two sentences that directly address purpose and usage without any wasted words. Every sentence adds clear value, making it efficient and well-structured for quick comprehension by an AI agent.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is largely complete. It covers the core purpose and usage guidelines effectively. However, it could be more complete by briefly mentioning the response format or any implicit constraints, though this is a minor gap for such a straightforward tool.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not mention any parameters, which is appropriate. A baseline of 4 is applied as it correctly omits unnecessary parameter details, though it could slightly enhance value by noting the lack of filters (e.g., no date ranges).

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's purpose with a specific verb ('get') and resource ('list of all tasks from OmniFocus'), including the scope ('including completed ones'). It distinguishes this tool from siblings like 'get_active_tasks' by explicitly mentioning completed tasks.

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 provides explicit guidance on when to use this tool: 'when the user explicitly asks for 'all tasks' or 'completed tasks'.' This directly addresses usage scenarios and implicitly suggests alternatives (e.g., 'get_active_tasks' for non-completed tasks), making it highly actionable for an AI agent.

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/mdoel/omnifocus-mcp'

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