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).
`on_behalf_of`	No	An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
`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.

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / on_behalf_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}

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

A3.9/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true). The description adds behavior beyond annotations by documenting the return shape (total, truncated, events) and the paging implication of `truncated` — valuable since no output schema exists. Does not mention auth or scoping caveats beyond what schema says.

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

Conciseness4/5

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

Three tight sentences, front-loaded with purpose, then usage, then return contract. No filler, though the return-value sentence is only partially leveraged given the schema already handles paging detail.

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

Completeness4/5

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

For a read-only search tool with full schema coverage, the description adequately covers purpose, two key use cases, and the non-trivial return contract (total/truncated/events). Minor gap: no mention of how results differ across agent_id/on_behalf_of scoping, but the schema covers that.

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?

Schema coverage is 100%, so the schema already documents all 8 parameters thoroughly. The description only adds meaning for one parameter (only_unnotified=True for digests); the rest of its parameter-related value duplicates the schema. Baseline 3 applies.

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

Purpose4/5

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

States a specific verb+resource: 'Search the user's monitor event log.' This clearly distinguishes it from generic search siblings, though it does not explicitly differentiate from near-neighbors like mark_monitor_events_notified or search_news_events.

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

Usage Guidelines4/5

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

Gives two concrete usage contexts: scheduled digests via only_unnotified=True and ad-hoc questions like 'what's the latest on Stripe?'. Clear usage guidance, but no explicit exclusions or named alternatives (e.g. when to use mark_monitor_events_notified instead).

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?