keepygaga
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listA | Return one complete live topics, areas, or people Route Catalog. No search, matching, pagination, Facts, or write versions. |
| readA | Use before mutation unless current Page Snapshots are already available. Read unique canonical paths together; returned files contain Facts, opaque write versions, and capacity signals. |
| createA | Create new dynamic pages after full-batch validation. On applied, reuse returned Page Snapshots and receipts; do not call read or list solely to verify success. |
| addA | Add independent Facts and optionally replace the page description using its latest Page Snapshot. Group Facts for one page in one operation. On applied, reuse returned Page Snapshots and receipts; do not verify with read or list. |
| updateA | Replace an exact Fact with an optional page description, update page metadata alone, or mechanically repair a repairable page using its latest version. On applied, reuse returned Page Snapshots and receipts; do not verify with read or list. |
| moveA | Move exact Facts and optionally replace source or existing-destination descriptions, or atomically create a bounded new destination. Preserve Fact dates and leave at least one source Fact. On applied, reuse returned Page Snapshots and receipts; do not verify with read or list. |
| renameA | Rename dynamic pages using latest Page Snapshots, one operation per page. On applied, reuse returned Page Snapshots and receipts; do not verify with read or list. |
| deleteA | Delete exact Facts with an optional page description, or delete dynamic pages, only after explicit current-turn user authorization. On applied, reuse surviving Page Snapshots and receipts; do not verify with read or list. |
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 8 tools
The tools are mostly distinct: list and read serve different read purposes, and create/add/update/move/delete each target specific fact or page operations. However, update, move, and delete each have secondary description-related behaviors, so an agent could occasionally hesitate between mutation tools without carefully reading the details.
All tool names are lowercase single-word imperative verbs: list, read, create, add, update, move, rename, delete. This is a highly consistent and predictable naming convention, with no mixed styles or vague generic names.
Eight tools is well within the ideal range for a content-management server covering facts and pages. Each tool occupies a distinct role in the read/create/update/delete lifecycle, and none feel redundant or excessive.
The surface covers core page and fact lifecycle operations well: read/list, create/add, update/move/rename, and delete. Minor gaps exist, such as no fact-level search or standalone fact listing, but agents can work around these by reading canonical page paths.