obituary
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| obit_buryA | Moves absolute paths into the restorable graveyard immediately, with the same Guard and identity checks as obit bury. |
| obit_extendB | Extends tracked lifespans by ID or absolute path, counted from now when already due. |
| obit_graveyardA | Lists burials and pending manifests together in ascending ID order; reconciles verified interrupted restores and reports their actual paths. Optional here filters original paths by an absolute directory, including descendants. Pass nextAfter as after and version to continue with the same here. changed warns when the full set changes; restart for a complete view. total counts this read. Permanent purging is a user decision. |
| obit_listA | Lists tracked items in ascending ID order; pass nextAfter as after and version to continue. changed warns when the full set changes; restart for a complete view. total counts this read. |
| obit_markA | Registers absolute paths with a lifespan, as obit add does. Re-registering resets expiry. Guard and identity checks apply. |
| obit_mktempB | Creates and registers a temporary directory with a lifespan. The explicit absolute cwd selects the Git project; outside Git the system temporary directory is used. |
| obit_proposalsA | Lists proposals in ascending ID order; pass nextAfter as after and version to continue. changed warns when the full set changes; restart for a complete view. total counts this read. Approval and rejection belong to the user, who executes obit approve or obit reject; this server cannot decide them. |
| obit_resurrectB | Restores verified burials by ID or absolute original path. Existing files are never overwritten; the result reports the restored path. |
| obit_spareB | Stops tracking IDs or absolute paths and leaves files in place. |
| obit_statsB | Reports tracked items, graveyard size, lifetime counters and delete guard counts. |
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 10 tools
Each tool maps to a distinct lifecycle action: mark registers, extend adjusts lifespan, bury moves to graveyard, resurrect restores, and spare stops tracking. The three listing tools (list, graveyard, proposals) share similar pagination semantics but target different collections, so confusion is limited.
All tools share the obit_ prefix and snake_case formatting, which is highly predictable. However, some names are nouns (graveyard, proposals, stats) while others are verbs (bury, extend, mark), so the verb_noun pattern is not perfectly uniform.
Ten tools is a well-scoped size for a file lifespan and graveyard management server. Each tool appears to earn its place by covering a specific lifecycle operation without obvious redundancy.
The surface covers registration, listing, extension, untracking, burial, restoration, graveyard viewing, temp creation, proposals visibility, and stats. Permanent purging and proposal approval are intentionally left to the user/CLI, so the main lifecycle is complete with only minor intentional gaps.