omnistate
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| omnistate_initC | Initialize OMNISTATE state governance and pre-commit guardrail in the current workspace. |
| omnistate_beginB | Begin a safe, transactional state change. Declares intent, scope boundaries, and risk tier. |
| omnistate_stepA | Record an intermediate progress milestone or action within the active transaction. |
| omnistate_auditB | Audit current modifications against scope boundaries, anti-laziness gates, and test suites. |
| omnistate_finishA | Finalize transaction, verify anti-tamper fingerprints, archive immutable snapshot, and issue commit clearance. |
| omnistate_abortB | Abort active transaction and optionally roll back uncommitted changes in scope. |
| omnistate_statusA | Get current OMNISTATE status, active transaction details, git head, and commit clearance state. |
| omnistate_inspect_diffB | Run anti-laziness and scope inspection on the working tree diff without altering state. |
| omnistate_explain_rulesA | Explain the OMNISTATE transaction lifecycle rules and guardrails for AI coding assistants. |
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 9 tools
Tools map cleanly to a transaction lifecycle (init, begin, step, audit, finish, abort) with status and inspect_diff as read-only helpers. The main possible confusion is audit vs inspect_diff, both involving scope/anti-laziness checks, and init vs begin, but descriptions distinguish state-changing versus read-only and setup versus transaction start.
All tools share the omnistate_ prefix and snake_case formatting, making the set highly predictable. Minor deviations exist: status is a noun while most names are verbs, init is abbreviated, and step is less action-specific, but the convention remains readable.
Nine tools fit comfortably within the ideal 3-15 range for a transaction-governance server. Each tool corresponds to a distinct lifecycle stage or helper, with no obvious filler.
The surface covers setup, transaction start, progress recording, auditing, commit clearance, abort/rollback, status, diff inspection, and rule explanation. A minor gap is that archived immutable snapshots are created but no tool lists or retrieves transaction history or past snapshots.