Sliq

Search Monitor Events

search_monitor_events

Read-only

Search the user's monitor event log. Use for scheduled digests (only_unnotified=True) and ad-hoc questions ('what's the latest on Stripe?').

Returns a dict with total (full match count), truncated (True when more rows exist past this page — page with offset to reach them), and events.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 50, max 200)
`since`	No	ISO datetime or natural language like 'last 7 days' (optional)
`offset`	No	Rows to skip for paging (default 0). When `truncated` is True, re-call with offset += limit to fetch the next page.
`agent_id`	No	Filter by specific monitor agent. Omit to search across all your agents (inside an agent run, an omitted agent_id defaults to that run's agent).
`company_domain`	No	Filter by company display name or domain — matches either (e.g. 'stripe.com' or 'Stripe'). Optional.
`min_confidence`	No	Minimum confidence score 1-10 (default 1)
`only_unnotified`	No	Only return events not yet included in a digest (default False)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / agent_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by specific monitor agent. Omit to search across all your\nagents (inside an agent run, an omitted agent_id defaults to that run's agent)."
+}

removedInput schema / properties / task_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Filter by specific monitor task. Omit to search across all your\ntasks (inside a task run, an omitted task_id defaults to that run's task)."
-}

First observedSep 15, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only provide readOnlyHint=true, which describes the safety profile but not behavior. The description adds important behavioral details: it returns a dict with specific keys (`total`, `truncated`, `events`), explains pagination via `truncated` and `offset`, and clarifies count semantics. This goes beyond the schema and gives the agent critical operational understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences: the first states the purpose, the second gives use cases, the third explains the return structure. It is front-loaded with the core action, and every sentence earns its place without fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, 100% schema coverage, and no output schema, the description covers the essential output shape and pagination, which is typically the missing piece. There are no extras like enums or nested objects to clarify. The description is complete for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already has 100% coverage with descriptive parameter descriptions, including defaults and usage notes (e.g., offset paging, agent_id fallback). The description adds a bit by mentioning 'only_unnotified=True' for digests, but the schema already explains each parameter. Baseline 3 is appropriate given the high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search the user's monitor event log' with a specific verb and resource. It distinguishes itself from sibling search tools by focusing on monitor events and hints at its use for digests. The first sentence is precise and prevents confusion with other search_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly mentions two use cases: scheduled digests and ad-hoc questions, giving the agent clear context when to use this tool. It also implies the alternative (using only_unnotified for digests) by highlighting the parameter. Although it doesn't name alternative tools, the sibling list makes it clear that other search tools exist, but the description's guidance is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sliq tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?