Skip to main content
Glama
someposer
by someposer

list_projects

Retrieve a comprehensive list of all projects in OmniFocus to organize and manage tasks efficiently using MCP OmniFocus server.

Instructions

List all projects in OmniFocus.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_projects'. This decorated function serves as the entry point for the tool, delegating the actual work to omnifocus.list_projects().
    @mcp.tool
    def list_projects() -> list[dict[str, str]]:
        """List all projects in OmniFocus."""
        return omnifocus.list_projects()
  • Core helper function implementing the logic to list projects by executing JavaScript in OmniFocus via evaluate_javascript, using shared common functions for status mapping.
    def list_projects() -> list[dict[str, str]]:
        """List all projects in OmniFocus.
    
        Returns:
            A list of dictionaries containing project names, ids, statuses, etc.
        """
        script = Template(
            dedent("""
        ${__common_functions__}
        
        (() => {
            return flattenedProjects.map(project => {
                return {
                    id: project.id.primaryKey,
                    name: project.name,
                    status: projectStatusToString(project.status),
                    flagged: project.flagged,
                    deferDate: project.deferDate ? project.deferDate.toString() : null,
                    dueDate: project.dueDate ? project.dueDate.toString() : null,
                    tags: project.tags ? project.tags.map(tt => tt.name) : [],
                };
            });
        })();
        """)
        )
    
        return evaluate_javascript(script.substitute(__common_functions__=__common_functions__))
  • Registration of the 'list_projects' tool using @mcp.tool decorator in the FastMCP server.
    @mcp.tool
    def list_projects() -> list[dict[str, str]]:
        """List all projects in OmniFocus."""
        return omnifocus.list_projects()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it lists projects but doesn't cover aspects like pagination, sorting, error conditions, or what 'all' entails (e.g., archived vs. active). This is a significant gap for a tool with zero annotation coverage.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it highly concise and well-structured for quick comprehension.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is minimal but adequate for basic listing. However, with no annotations and no output schema, it lacks details on behavior, return format, or error handling, making it incomplete for reliable agent use.

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 the schema fully documents the absence of parameters. The description doesn't add parameter details, but with no parameters, a baseline of 4 is appropriate as there's nothing to compensate for.

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 clearly states the verb ('List') and resource ('all projects in OmniFocus'), making the purpose unambiguous. It doesn't distinguish from siblings like 'list_tasks_by_project' or 'list_perspectives', which would require a 5, but it's specific enough for basic understanding.

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. It doesn't mention siblings like 'list_tasks' or 'list_tasks_by_project', nor does it specify contexts or prerequisites for listing projects, leaving the agent to infer usage.

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

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

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