Sagas over MCP: where is this instance, and what is it waiting on? New in 1.18.0
Find a Wolverine saga instance in a CritterWatch-monitored fleet and explain where it is with the list_sagas / list_saga_instances / get_saga_instance MCP tools (CritterWatch 1.2): which sagas each service runs and the messages they handle, a bounded peek at a saga type's instances (an arbitrary set, not the newest) or a query over the saga's own state (where / orderBy / arguments / page, where the saga storage can filter), and one instance's state, executed messages, pending timeouts and outstanding messages in one call.
Use when asked 'where is order saga X', 'what is this saga waiting on', 'why did this workflow stall', or 'which sagas are stuck'. Covers the peek versus the query, CriteriaRefused (never an unfiltered answer), the sources block and the not-observed-is-not-did-not-happen discipline, ExplorerDisabled and NoResponse, finding the saga's conversations (list_conversations sagaId) and scheduled messages (query_scheduled_messages sagaId), traces, and the mcp.sagas.read capability.
Skill details
- Skill name:
wolverine-integrations-critterwatch-sagas - Applies to:
wolverine,marten,polecat,fisher - Tags:
critterwatch,mcp,sagas,workflow,diagnostics,conversations,tracing,agents,saga-query,timeouts,scheduled-messages - Added in: 1.18.0
- License: Proprietary. Copyright JasperFx Software LLC.
