Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SAGA_HOSTNoHost for SSE transport.
SAGA_PORTNoPort for SSE transport.
SAGA_DATABASENoPath to the SQLite database file. Alternative to --database.
SAGA_TRANSPORTNoTransport type: stdio (default) or sse.stdio
SAGA_ACTIONS_FILENoPath to the actions configuration file. Alternative to --actions.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
begin_sagaB

Start a durable transactional workflow.

execute_saga_stepC

Immediately execute an action after current governance, schema, and action-policy checks.

plan_saga_stepB

Persist a version-pinned workflow node; governance may add an approval gate or reject the plan.

run_ready_stepsC

Re-evaluate current governance and execute ready DAG nodes in bounded dependency waves.

approve_saga_stepC

Approve or reject a workflow node; approvals are subject to tenant governance while rejection remains fail-safe.

retry_saga_stepC

Return a failed/rejected/blocked workflow node to scheduling after current governance checks.

checkpoint_sagaC

Persist a named workflow checkpoint and operator/agent-provided checkpoint data.

commit_sagaC

Commit a completed saga after current tenant governance checks.

rollback_sagaC

Compensate saga steps in reverse order; rollback remains available as the safety path.

trigger_rollbackB

Immediately start compensation after a client-detected failure.

get_sagaA

Inspect saga, workflow DAG, checkpoints, action versions, results, approvals, and recovery state.

get_saga_timelineC

Inspect a payload-safe timeline combining steps, workflow nodes, audit evidence, and integrity status.

get_audit_eventsC

Read append-only audit events without exposing action inputs, results, or secret material.

verify_audit_chainC

Verify the per-saga SHA-256 audit hash chain.

get_policy_statusB

Inspect the effective governance backend, revision, budgets, approval threshold, and rule ids for the caller tenant.

get_policy_decisionsB

Read durable governance decisions and safety overrides for one tenant-owned saga.

list_actionsA

List active action contracts, schemas, semantic effects, risk, hashes, and execution policies.

get_actionA

Inspect one registered action contract by id and optional version.

Prompts

Interactive templates invoked by user choice

NameDescription
saga-coordinatorWrap multi-step side effects in the Saga Coordinator. Inspect actions and governance before execution. Use `plan_saga_step` for governed workflows because policy can require approval based on action risk, tenant rules, or budgets. Obtain approvals when required, then call `run_ready_steps`; current policy is re-evaluated before side effects. Use `get_policy_status` and `get_policy_decisions` for governance evidence, and `get_saga_timeline` plus `verify_audit_chain` for operational review. If a saga enters RECOVERY_REQUIRED, reconcile the external outcome before forcing a retry; rollback remains available for compensation safety.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ananthaprakashb/semantic-saga-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server