Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
omnifocus_get_tasksB

Get tasks from OmniFocus. Filter by flagged, due today, or all. Detected version: standard

omnifocus_create_taskB

Create a new task in OmniFocus. Detected version: standard

omnifocus_update_taskA

Update an existing task in OmniFocus. (Standard version: changes via SQLite won't sync until OmniFocus restart)

omnifocus_complete_taskB

Mark a task as complete. (Standard version: changes via SQLite won't sync until OmniFocus restart)

omnifocus_get_projectsA

Get list of active projects from OmniFocus. Detected version: standard

omnifocus_get_configB

Get current configuration settings

omnifocus_set_configA

Update configuration settings. For Standard version: directSqlAccess controls whether to use direct SQLite access for update/complete operations (faster but requires OmniFocus restart to sync)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct resource and action: tasks have get/create/update/complete, projects have get, and configuration has get/set. There is no meaningful overlap between the tools, so an agent should be able to select the right one without confusion.

Naming Consistency5/5

All tools follow the consistent omnifocus_<verb>_<noun> snake_case pattern using clear verbs like get, create, update, complete, and set. The naming conventions are uniform and predictable across the entire set.

Tool Count5/5

Seven tools is a well-scoped size for an OmniFocus server, covering task operations, project retrieval, and configuration without unnecessary bulk. Each tool serves a clear purpose and the count feels appropriate for the domain.

Completeness4/5

The core task lifecycle is covered well with get, create, update, and complete operations, and config get/set supports the server itself. Minor gaps exist such as no task deletion or project mutation capabilities, but agents can likely work around these for most workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues