Skip to main content
Glama

perspective_create

Create a custom OmniFocus perspective with specified name, rules, aggregation, and icon color. Returns the new perspective's ID.

Instructions

Create a new custom OmniFocus perspective with the given name, optional rule tree, optional aggregation, and optional icon color. The shell is created via JXA make (the only supported create path) and rules + aggregation + iconColor are written via OmniJS in the same transport hop — if rule writing throws, the shell is rolled back so the database is never left with a half-configured perspective. Use BEFORE composing complex authoring flows: pair with perspective_get to clone an existing perspective, or with perspective_delete to replace one. Do NOT use to update an existing perspective — prefer perspective_update (slice C) when it lands. rules is the same shape perspective_get returns (atom | aggregate | disabled wrapper) — round-trips are lossless. Each rule atom may set at most one action* predicate; combine predicates by wrapping atoms in a RuleAggregate with aggregateType all/any/none. Tag-id and focus-id arrays must be non-empty with non-empty entries. Returns { id } — the persistent identifier of the new custom perspective. Side effects: creates a perspective in OmniFocus; invalidates the perspective cache; sets meta.syncPending = true. Custom perspectives require OmniFocus Pro — without it, the adapter throws FeatureRequiresPro. Example: perspective_create({ name: "Today's plate", aggregation: "all", rules: [{ actionStatus: "flagged" }] })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for the new perspective. Must be non-empty and unique within the OmniFocus database — duplicate names are rejected with VALIDATION_ERROR.
rulesNoTop-level rule list. Empty array means 'show everything' (the default for fresh perspectives). Each rule is an atom (single action* predicate), an aggregate (compound rule with aggregateType + aggregateRules), or a disabled wrapper around either.
iconColorNoCustom icon color in [0, 1] floats { r, g, b, a }. Omit for the OmniFocus-assigned default.
aggregationNoTop-level rule aggregation. One of "all", "any", "none". Defaults to "all" when omitted.
Behavior5/5

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

With no annotations, the description fully discloses behavior: JXA make for shell, OmniJS for rules/aggregation/iconColor, rollback on failure, side effects (invalidate cache, set syncPending), return value, and prerequisite (Pro).

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 comprehensive yet well-structured: purpose, creation process, usage, rule details, return, side effects, requirements, example. Every sentence adds value without redundancy.

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

Completeness5/5

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

For a tool with 4 parameters, nested objects, and no output schema, the description covers all essential aspects: purpose, input constraints, behavior, error handling, side effects, return value, and prerequisites. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. Description adds significant meaning: explains rules shape matches perspective_get, constrains atoms to one action* predicate, describes aggregate and disabled wrappers, and gives an example. Provides context beyond schema.

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 creates a new custom OmniFocus perspective with name, optional rules, aggregation, and icon color. It distinguishes itself from update and delete siblings, and explains its role in authoring flows.

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?

Provides explicit when-to-use guidance: pair with perspective_get to clone or perspective_delete to replace, and do not use for updates (prefer perspective_update). Also notes the OmniFocus Pro requirement.

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

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