Skip to main content
Glama

YouSpot

by com.youspot

Get calendar events

get_calendar_events
Read-only

List events from the user's connected Google Calendar, ordered by start time — summary, start/end, location, organizer, attendees and their RSVP status, and a meeting link when there is one. With no time range it returns upcoming events from now. time_min and time_max are RFC3339 timestamps ('2026-08-19T00:00:00Z'), so 'what's on my calendar tomorrow' is time_min/time_max spanning that day; past ranges work too. query free-text matches event titles, descriptions, and attendees. For 'how many meetings…' questions over long ranges (a quarter, a year), set count_only=true — it sweeps the whole range and returns the total plus a per-month breakdown instead of the events themselves, so a 12-month count is one call. By default this reads the primary calendar; to read a named calendar ('my Family calendar'), first get its id from list_google_calendars, then pass calendar_id. If the result says no Google account is connected (or the account lacks calendar access), show the user the message and link them to /user/integrations/gmail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text search over events (titles, descriptions, attendees). Omit to list everything in the range.
accountNoEmail address of one connected Google account. Omit to read all connected accounts.
time_maxNoLatest event start, RFC3339.
time_minNoEarliest event end, RFC3339 ('2026-08-19T00:00:00Z'). Defaults to now when time_max is also omitted.
count_onlyNoReturn only counts — total and per calendar month — instead of the events. Sweeps far more of the range (up to 12,500 events) than an event listing can. Use for totals and "how many" questions.
calendar_idNoWhich calendar to read — an id from list_google_calendars. Omit for the primary calendar.
max_resultsNoMax events to return (default 10, max 250).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the burden of behavioral disclosure and does so thoroughly: events are ordered by start time, count_only sweeps up to 12,500 events and returns a per-month breakdown instead of events, and the disconnected-account error handling is specified with a user-facing action. This goes well beyond the annotation.

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?

The description is dense but every sentence earns its place: it front-loads the core purpose and output, then layers defaults, time-range semantics, query behavior, count-only mode, calendar selection, and error handling in a logical order. The length is justified by seven parameters and no output schema.

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 fully covers return content, default behavior, count-mode output, named-calendar prerequisites, and failure handling. The schema supplies the remaining parameter details (account email, max_results), so an agent has everything needed to select and invoke the tool correctly.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds substantial practical meaning: time_min/time_max get an RFC3339 example and a natural-language mapping ('what's on my calendar tomorrow'), query scope is expanded to titles, descriptions, and attendees, and calendar_id is explicitly tied to the output of list_google_calendars. The count_only parameter is explained with its range-sweeping behavior and ideal use cases.

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?

The description uses a specific verb and resource: 'List events from the user's connected Google Calendar' and enumerates the returned fields (summary, start/end, location, organizer, attendees/RSVP, meeting link). It clearly distinguishes this read/list tool from siblings like create_calendar_event and update_calendar_event without relying on the title.

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?

The description gives explicit when-to-use guidance: no time range means upcoming events from now, count_only=true for 'how many meetings' questions over long ranges, and list_google_calendars is referenced as the prerequisite step for reading a named calendar. It also explains that past ranges work, so an agent knows the tool supports both backward and forward queries.

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

All YouSpot toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear boundaries even within overlapping domains like LinkedIn (search vs. free-form query vs. profile vs. summary) and graph deletion (soft single, bulk soft, permanent single). Descriptions explicitly cross-reference related tools to prevent misselection.

Naming Consistency4/5

The vast majority follow a consistent verb_noun pattern (get_, list_, search_, create_, delete_, etc.). A few noun-phrase exceptions like linkedin_analytics, mutual_connections, similar_objects, and what_needs_attention deviate slightly, but they are still descriptive and do not create confusion.

Tool Count2/5

At 66 tools this is far beyond the 25+ threshold considered too many, even though the server covers many integration domains. Each domain has a coherent subset, but the overall surface is heavy for agents to navigate and would benefit from consolidation or namespacing.

Completeness4/5

The set provides deep read/search coverage across Gmail, Slack, Calendar, LinkedIn, HubSpot, Obsidian, Twitter, and a graph store, with core write operations for calendar, drafts, Slack, and graph objects. Minor gaps exist—notably no calendar delete, no direct Gmail send to third parties (only drafts), and no LinkedIn post/message actions—but these appear deliberate and do not block typical workflows.

Resources