Sliq

Search calendar

search_calendar

Read-only

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "where_clause": "<where_clause>"
    },
    "name": "search_calendar"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (default 50, max 200). Only override if user says specific number like "show me 10 events". 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: event_start DESC)	event_start DESC
`on_behalf_of`	No	A teammate's email, or an agency client's from list_agency_clients, to run this call in that 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, subject, event_start, event_end, location, meeting_link, organizer, attendees, is_all_day, is_cancelled, has_recurrence. For organizer/attendees JSONB, use: organizer::text ILIKE '%pattern%' or attendees::text ILIKE '%pattern%'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / on_behalf_of / description

Previous value: -"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."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description usefully discloses the return shape (count, truncated flag, events array) which is valuable since no output schema exists, but it says nothing about permissions, on_behalf_of account behavior, or pagination beyond what the schema already documents.

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?

Two short, front-loaded blocks with no filler; the summary states the action first and the returns block is compact. The XML-style wrapping is slightly verbose for the amount of content but does not impede comprehension.

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

Completeness3/5

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

For a filtered search tool with no output schema, disclosing count/truncated/events is the right call and largely completes the picture. What is missing is the routing context an agent needs to pick this tool over search_meetings, which leaves the definition adequate but not complete.

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 every parameter already carries its own description including the allowed where_clause columns and JSONB casting syntax. The description only echoes the instruction to use those exact column names, adding emphasis but no new meaning.

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 calendar events') plus the backing table, which distinguishes this read operation from siblings like create_calendar_event and update_calendar_event. It does not, however, mention the closest read-only sibling (search_meetings) so the boundary there is left implicit.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing tells the agent how this differs from search_meetings or when calendar search is preferred over other lookup tools. Usage is only implied by the tool name and the where_clause instruction.

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?