NoFuss for OmniFocus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nofuss_getA | Get 1–20 exact IDs with per-ID outcomes, preserving order and duplicates. entity defaults to task; project returns metadata for any state. Optional tree accepts one project ID: all descendants in native sibling preorder, including completed/dropped work. Tree has its own task view/fields/limit/cursor; follow its live continuation to completion. Brief by default; fields overrides view. Project brief: name/status/type/folder_id; detail adds notes/tags/dates, native direct counts and review interval. Project roots are excluded from task rows. Notes/name use Unicode text windows; tag_ids/notifications use collection windows on exact gets. Follow truncated[field].next_cursor with the matching text/collection field and ID. Unavailable fields are explicit. |
| nofuss_queryA | Query tasks in inbox_roots or one exact project, or projects in library (including nested folders). Project inventories default to all statuses/flags; optional status and flagged filters combine with AND, including flagged:false. Project records reuse exact-get projections. Task project depth defaults to descendants; direct selects immediate children. Tasks exclude project roots and locally dropped work; include_completed admits local completion. Ancestors do not prune tasks. Order: created_at ASC (null first), then ID. Follow live query-bound cursors to completion. |
| nofuss_overviewA | Workload overview in one fresh read: unfinished Inbox roots and all active library projects, including nested/inactive folders. Full-scope counts; one compact project list with next_review_at, review_due (at evaluated_at), and work_state. Remaining work excludes native Completed/Dropped descendant task statuses; available actions have Available/Next/DueSoon/Overdue status, including groups, excluding project roots. Optional waiting_tag_ids (1–20 exact IDs, match any native task tag) adds full-scope waiting counts and compact task IDs; omitted means not requested, never zero. No ancestor-tag expansion or priority judgment. Counts stay complete when list coverage is byte-limited; drill down using nofuss_query active library and nofuss_get project trees. No notes or notifications. |
| nofuss_statusA | Observe build/readiness, implemented operations, fresh native declaration support and build-scoped verification/gaps. Declarations do not prove behavior. No private traces, sync trigger or claim of sync completion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools occupy mostly distinct niches: nofuss_get fetches by exact IDs, nofuss_query filters by inbox/project/library, nofuss_overview returns aggregate workload counts, and nofuss_status reports build/readiness. The boundary between nofuss_query and nofuss_overview is somewhat blurry since both read tasks and projects, but the descriptions clarify that overview is a fresh-read summary and query is a drill-down.
All tools share the nofuss_ prefix with snake_case single-word suffixes, giving a predictable pattern. The minor deviation is that get/query read as verbs while status/overview read as nouns, but the convention is still clearly consistent.
Four tools is a compact, coherent set for what appears to be a read-only inspection server, and each earns a place (exact fetch, filtered query, overview, status). It is slightly thin and could arguably merge overview into query, but nothing is redundant or bloated.
Read coverage is solid (exact gets, filtered queries, tree traversal, aggregate overview, status), but there are no mutation tools such as create/update/complete/delete task or project. If the server is intentionally read-only this is fine, but for an OmniFocus task-management domain the surface leaves notable gaps.