Living Stack Community
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| livingstack.statusA | Inspect Community capabilities and the paid boundary. |
| livingstack.session_startA | Start an isolated proof session with an immutable scope and budget. |
| livingstack.session_statusB | Verify a session lifecycle, budget, counts, and ledger head. |
| livingstack.authorize_actionA | Gate one local host action against scope risk and budget; never executes it. |
| livingstack.record_outcomeA | Consume one authorization and bind its observed result to typed evidence. |
| livingstack.check_claimA | Check a proposed claim against explicitly selected, fresh, successful, subject-bound evidence. |
| livingstack.session_closeB | Close a proof session and preserve its tamper-evident local ledger. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Living Stack Community capabilities |
TDQS
Scored across 7 tools
Each tool maps to a unique stage or resource: community status, session lifecycle, authorization gating, outcome recording, claim checking, and session closure. Even the two status-like tools are cleanly separated by global vs per-session scope, so an agent should not confuse them.
All tools share a consistent `livingstack.` prefix and snake_case, but the word-order convention is mixed: `authorize_action`, `record_outcome`, and `check_claim` are verb-first, while `session_start`, `session_status`, and `session_close` are noun-first and `status` is a bare noun. The names are readable and grouped, but they do not follow a single predictable pattern.
Seven tools is well-scoped for a proof-session lifecycle: one for capabilities, three for session lifecycle, and three for the authorize/record/check workflow. Each tool adds a distinct capability with no apparent redundancy or bloat.
The set covers the full workflow from starting a session through authorizing an action, recording its outcome, checking a claim, and closing the session without creating dead ends. Status and session_status provide the needed verification points, and there are no obvious missing operations for the stated domain.