Sliq

Query Monitored Companies

query_monitored_companies

Read-only

mode="search" (default): individual company rows. mode="stats": aggregate counts, with optional group_by for analytics.

Columns: display_name, domain, stage ('active'/'removed'), data (JSONB), agent_id, created_at, updated_at. JSONB queries: data->>'last_sweep_status' = 'error'. For outreach prospects, call query_prospects. In search mode, {count, truncated, items array}. In stats mode, {total, by_stage: {active: N, removed: M}, groups?: {: {total, by_stage}}}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	"search" to list rows, "stats" for aggregate counts.	search
`limit`	No	Max results (default 50, capped at 100). Search mode only.
`offset`	No	Rows to skip for paging (default 0, search mode only). When the result is truncated, re-call with offset += limit for the next page.
`agent_id`	No	Filter to a specific agent. Omit for cross-agent queries.
`group_by`	No	(stats mode only) JSONB data key to group by; each group carries the same by_stage map as the top-level stats.
`order_by`	No	SQL ORDER BY (default: created_at DESC). Search mode only.	created_at DESC
`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.
`where_clause`	No	SQL WHERE condition (default: all). Examples: "stage = 'active'", "domain ILIKE '%.io'"	1=1

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026
- addedInput schema / properties / mode / title
```
Added value: +"QueryMode"
```

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 to a specific agent. Omit for cross-agent queries."
+}

removedInput schema / properties / task_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Filter to a specific task. Omit for cross-task queries."
-}

First observedSep 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries most of the load and does so: it discloses that search results can be truncated, describes the shape of both return modes, and shows the JSONB access syntax needed to filter. It stops short of stated row caps or performance caveats, which are instead found in the schema.

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?

Front-loaded summary with mode semantics, then columns, then a compact returns block. Sentences are dense with usable information (mode defaults, JSONB syntax, sibling pointer) and nothing is redundant.

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?

No output schema exists, yet the description supplies both return shapes, the truncation signal, and pagination context (offset guidance lives in the schema). For an 8-parameter read-only query tool, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real value by listing the available columns (display_name, domain, stage, data, agent_id, created_at, updated_at) and giving a concrete JSONB predicate example, which directly informs how to write where_clause and order_by. That goes beyond what the schema alone conveys.

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 and resource ('Query an agent's monitored companies') and enumerates two modes with the default. It distinguishes itself from query_prospects, but says nothing about how it differs from the very similar sibling query_companies, leaving that ambiguity for the agent to resolve.

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?

Explains when to pick each mode (rows vs aggregate counts) and explicitly routes outreach lookups to query_prospects. Missing explicit guidance on choosing between this and query_companies/query_agent_people, but the mode selection and exclusion are clearly stated.

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?