Sliq

Search Meetings

search_meetings

Read-only

When the user has Grain, Granola, or Otter connected, prefer this tool first (Fathom data is local and faster) and fall back to grain_*/granola_*/otter_* only if no relevant results or the user explicitly references that source. Dict with count, truncated, and meetings array (summary truncated to 6000 chars, transcript truncated to 10000 chars — use get_meeting_transcript(id) to fetch the full transcript for a specific meeting)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (default 10, max 20). Only override if user says a specific number like "show me 5 meetings". For vague quantities ("couple", "few", "recent"), omit this parameter to use default.
`offset`	No	Rows to skip for paging (default 0). When the result is truncated, re-call with offset += limit to fetch the next page.
`order_by`	No	SQL ORDER BY clause (default: meeting_date DESC)	meeting_date 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`	Yes	SQL WHERE clause (without WHERE keyword). Use ONLY these columns: provider, title, meeting_date, duration, speakers, attendees, meeting_url, share_url, summary, transcript. For speakers/attendees JSONB, use: speakers::text ILIKE '%pattern%' or attendees::text ILIKE '%pattern%'

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."
+}

First observedSep 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description then adds genuinely new behavioral detail: results are truncated (summary to 6000 chars, transcript to 10000 chars), the response shape includes count/truncated/meetings, and get_meeting_transcript is the escape hatch for full transcripts. It does not restate anything the annotations already provide, though it stays silent on rate limits or cost of the query.

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?

Purpose and the routing rule are front-loaded in the summary block, and the returns block is short and information-dense with no filler. The XML-style scaffolding is slightly heavier than plain prose would be, but every sentence carries a distinct instruction.

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?

With no output schema, the description carries the return-value burden and does so: it names the dict keys, the truncation limits, and the follow-up tool. Combined with full schema coverage for parameters, an agent has what it needs to call and page correctly, though the truncation/pagination interaction could be stated a touch more explicitly.

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 description coverage is 100%, so every parameter (limit, offset, order_by, on_behalf_of, where_clause) is already documented in the schema. The description only re-emphasizes the where_clause column restriction, which duplicates the schema text rather than adding syntax examples or edge-case guidance. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Search user's meeting data from table_meeting_data') and scopes it to a named data table, which is enough to separate it from generic query/search siblings like query_search_results or search_calendar. It does not, however, explicitly contrast itself with the closest relevant sibling, get_meeting_transcript, except incidentally in the returns block.

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?

Gives an explicit preference rule and fallback condition: prefer this tool first when Grain/Granola/Otter are connected, and fall back to grain_*/granola_*/otter_* only when no relevant results appear or the user names that source. That is a real when-to-use / when-to-switch decision an agent can act on without opening any schema.

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?