Pachakutech Presence
OfficialServer 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 |
|---|---|
| manifestHighlightA | Ephemeral Manifestation. Draws a bounded, temporary highlight over the described on-screen content. Prefer this over describing a location in text when the user can see their screen. |
| spawnPresenceA | Instanced Manifestation, step 1 of 3 (spawn / animate / retire). Creates a persistent presence derived from the given context (e.g. 'a character based on what's on screen'). Optionally built from a held artifact (see addArtifact) rather than derived fresh. Returns a presenceId — pass it to animatePresence and retirePresence. The generative work (what the presence actually looks like) happens inside this contract; the contract itself never changes. |
| addArtifactA | Instanced Manifestation, step 1 of 2 (add / retire). Adds a Gaussian splat artifact (or other content asset) to the substrate as reference material — it is held, not rendered. Use this to give spawnPresence something concrete to build from (e.g. 'this is what I want the presence to look like') rather than describing appearance in prose. Returns an artifactId. |
| retireArtifactB | Instanced Manifestation, step 2 of 2. Removes a held artifact and frees its slot. |
| animatePresenceA | Instanced Manifestation, step 2 of 3. Feeds new content (e.g. words to say) to a presence created by spawnPresence. |
| retirePresenceA | Instanced Manifestation, step 3 of 3. Cleanly ends a presence created by spawnPresence and frees its slot. Always call this when the presence is no longer needed — concurrent live presences are capped. |
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 6 tools
Each tool targets a distinct resource and lifecycle stage: artifacts are added/retired, presences are spawned/animated/retired, and manifestHighlight covers a separate ephemeral display. The lifecycle hints in the descriptions make the boundary between artifact management and presence management clear.
All six tools use a consistent camelCase verb-noun pattern, such as addArtifact, retirePresence, and spawnPresence. The resource-specific roots (artifact, presence, highlight) are kept uniform, so there are no mixed conventions or vague generic verbs.
Six tools is well-scoped for a presence server: two artifact lifecycle tools, three presence lifecycle tools, and one ephemeral display tool. Each tool serves a distinct purpose, and none feels redundant or like filler.
Core lifecycles are covered: artifacts have add/retire, presences have spawn/animate/retire, and the highlight feature is available for ephemeral display. The only notable gap is the lack of a list/query tool for current artifacts or active presences, but agent workflows can work around that with returned IDs.