Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Get Luma events

get_luma_events
Read-only

Fetches every page (no truncation), so the returned list is the complete calendar — upcoming and past events alike. Use it to answer "which event is next", to find an event's id for get_luma_guests, or when a luma_event_created trigger fires and you need the full event context. Dict with events array and count. Each event dict is Luma's event object, the useful fields being: id (starts with "evt-", the key get_luma_guests takes), name, start_at / end_at (ISO 8601 UTC), timezone (IANA), url (the lu.ma page), location_type, meeting_url, visibility, registration_open, require_approval, spots_remaining, description_md.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_luma_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
on_behalf_ofNoA 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field 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."
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds real behavioral context beyond that: it fetches every page with no truncation, covers both upcoming and past events, and returns results in reverse-chronological order. Missing only operational details such as latency or volume limits on a full-calendar fetch.

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?

Front-loads the one-line summary, then separates usage from return shape in clearly labelled blocks. The returns section is long but earns its place since no output schema exists; the XML-style tags add slight verbosity without harming scanability.

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?

With no output schema, the description compensates by enumerating the useful fields of the returned event object, including the `evt-` id prefix that get_luma_guests consumes, timestamps in ISO 8601 UTC, and timezone format. Nothing an agent needs to call this tool and use its result is missing.

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% and the single `on_behalf_of` parameter is fully documented in the schema itself. The description adds no further meaning about that parameter, so the baseline 3 applies — correct but no extra value.

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 ('List all events on the user's Luma calendar') plus ordering ('most recent first') and completeness ('every page, no truncation'). It also names the adjacent tool get_luma_guests, so an agent can tell which one yields events versus guests without opening a schema.

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 three concrete when-to-use conditions: answering 'which event is next', sourcing an `id` for get_luma_guests, and responding to a luma_event_created trigger. It does not state when NOT to use it, e.g. versus the sibling search_calendar, so it stops short of full routing guidance.

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