Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Create Calendar Event

create_calendar_event
Destructive

Use search_emails or search_calendar to find email addresses for prior attendees. For new attendees whose email you don't have, use find_email. Dict with success status and event details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoOptional event description/notes (plain text)
subjectYesEvent title
locationNoOptional event location
providerNoWhich calendar to use ('outlook' or 'google'). Only needed if the user has both connected -- ask them which to use, then pass it here.
attendeesNoOptional list of attendees. Each is an object with required "email" and optional "name". Examples: [{"email": "alice@acme.com", "name": "Alice Smith"}] or [{"email": "alice@acme.com"}].
in_personNoALMOST ALWAYS OMIT THIS PARAMETER or set to false. ONLY set to true if the user literally says "in-person", "in person", "at my office", or "no video link". If there is ANY ambiguity, do NOT set this to true. A video meeting link is automatically added when this is false (the default).
end_datetimeYesEnd time as ISO 8601 in the user's LOCAL timezone, not UTC (e.g., "2026-02-17T11:00:00"). Do not include a timezone offset or Z suffix. Default to 30 minutes after start if user does not specify.
on_behalf_ofNoAn 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.
start_datetimeYesStart time as ISO 8601 in the user's LOCAL timezone, not UTC (e.g., "2026-02-17T10:00:00"). Do not include a timezone offset or Z suffix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
+}
    • changedInput schema / properties / provider / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "outlook",
-      "google"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "outlook",
+      "google"
+    ],
+    "title": "Provider",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations (readOnlyHint=false, destructiveHint=true) by disclosing the auto-included video link, the in_person override semantics, and a mandatory confirmation workflow. It does not address reversibility or failure modes, but the added context is substantial for a mutation tool.

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 with the core action, then constraints, then related-tool routing, wrapped in clean summary/returns sections. Every sentence carries actionable content with no padding.

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 9-parameter mutation tool with no output schema, it covers creation semantics, provider choice, video-link behavior, attendee sourcing, and confirmation. It omits edge-case behavior such as duplicate/conflicting events or error handling, leaving a small gap.

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 the baseline is 3. The description restates the in_person/video-link coupling already documented in the schema and adds no syntax, format, or default guidance for subject, body, or datetimes beyond what the properties already carry.

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?

States a specific verb and resource ('Create a calendar event in the user's connected calendar') and immediately scopes it to Outlook or Google. The automatic video-link behavior further distinguishes it from read-side siblings like search_calendar.

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?

Explicit invocation rules: always show details and get confirmation first, use search_emails/search_calendar to source prior attendee addresses, and find_email for new attendees. It names the exact alternative tools and the condition that selects each.

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

All Sliq toolsInspect
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