Reading documents through the console New in 1.15.0
Read a monitored service's stored documents through CritterWatch's document explorer MCP tools — list_document_types, query_documents and get_document — and filter or sort them on the document's own properties with where / orderBy / arguments (CritterWatch 1.1, jasperfx#869). The predicate is Dynamic LINQ text applied by the service's own store (Marten, Polecat or Fisher) through its LINQ provider, so member names are the C# ones and casing, enum storage, tenancy, soft deletes and hierarchies are the store's business.
Use when asked what a document holds, to find documents matching a condition, to page or sort a document type, or to explain a CriteriaRefused answer. Covers the dialect, typed @n arguments, what each store refuses rather than answer wrongly (SQL null semantics, date parts, enum ordering when stored as names), honesty fields (totalCount, notice, rows metadata, CriteriaRefused with a position, Timeout vs ServiceError), store / tenant / soft-delete addressing, the mcp.documents.read capability and the audit trail, and when to reach for query_sql instead.
Skill details
- Skill name:
wolverine-integrations-critterwatch-document-explorer - Applies to:
wolverine,marten,polecat,fisher - Tags:
observability,critterwatch,mcp,documents,querying,linq,diagnostics,agents - Added in: 1.15.0
- License: Proprietary. Copyright JasperFx Software LLC.