Skip to main content
Glama
someposer
by someposer

list_perspectives

Retrieve all perspectives in OmniFocus to organize and manage tasks effectively using MCP OmniFocus automation capabilities.

Instructions

List all perspectives in OmniFocus.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The list_perspectives tool is registered as an MCP tool using the @mcp.tool decorator. This is the entry point handler that delegates to the omnifocus module.
    @mcp.tool
    def list_perspectives() -> list[str]:
        """List all perspectives in OmniFocus."""
        return omnifocus.list_perspectives()
  • The core handler function that executes the JavaScript script to list all built-in and custom perspectives in OmniFocus via evaluate_javascript.
    def list_perspectives() -> list[str]:
        """List all perspectives in OmniFocus.
    
        Returns:
            A list containing the list of perspective names.
        """
        script = dedent("""
        (() => {
            let perspectives = new Array();
            perspectives = perspectives.concat(Perspective.BuiltIn.all);
            perspectives = perspectives.concat(Perspective.Custom.all);
            return perspectives.map(perspective => perspective.name);
        })();
        """)
    
        return evaluate_javascript(script)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'List all perspectives' implies a read-only operation that returns all available perspectives, but it doesn't specify whether this is paginated, sorted, filtered, or what format the output takes. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 that states exactly what the tool does with zero wasted words. It's appropriately sized for a simple list operation and front-loads the essential information. Every word earns its place.

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?

For a simple list operation with no parameters and no output schema, the description is minimally adequate but has clear gaps. It doesn't explain what perspectives are in OmniFocus context, doesn't describe the return format, and provides no usage guidance relative to sibling tools. With no annotations and no output schema, more context would be helpful.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't mention parameters since there are none, which is correct. The baseline for 0 parameters with full schema coverage is 4.

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 the resource 'perspectives in OmniFocus', making the purpose immediately understandable. It distinguishes from siblings like list_tasks or list_projects by specifying perspectives, but doesn't explicitly differentiate from other list operations beyond the resource name.

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. With siblings like list_tasks, list_projects, and list_tags, there's no indication of what perspectives are or when one would list them instead of other resources. The description simply states what it does without contextual usage information.

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