Skip to main content
Glama

search_events

Search the user's calendar events across all connected calendars, with description, location and attendees. Use it for questions the plan alone cannot answer: what a meeting is about, who is invited, when did I last meet X, what is in my private calendar, all-day entries like vacation. Only events from about 30 days back to 90 days ahead are available. Returns at most 50 events, soonest first; call get_event for the full text of one.

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": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast local date, YYYY-MM-DD; default 14 days after from, at most 120 days
fromNoFirst local date, YYYY-MM-DD; default today
limitNo
queryNoWords to find in title, description, location, attendee names or e-mails
calendarIdNoOnly this calendar (id from list_sources)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior1/5

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

The description says 'Search' events, which implies a non-mutating read operation, while the annotations declare readOnlyHint=false, meaning the tool is not read-only. That mismatch is a direct behavioral contradiction; despite useful details about time bounds and result caps, the rubric requires a score of 1 when the description contradicts annotations.

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 three dense but purposeful sentences, front-loaded with the core action and scope. Every sentence contributes either search scope, usage guidance, availability constraints, or follow-up routing, with no visible padding.

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?

For a tool with no output schema, the description covers what is searchable, the effective time window, the maximum result count, the ordering, and where to get full event text. An agent has enough information to invoke it correctly and interpret the result shape at a high level.

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

Parameters4/5

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

Schema coverage is 80%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: effective availability from about 30 days back to 90 days ahead, a maximum of 50 results, soonest-first ordering, and a pointer to get_event for full text. These details clarify how from, to, and limit behave in practice.

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 ('Search the user's calendar events across all connected calendars') and names the fields searched. It distinguishes itself from the plan ('questions the plan alone cannot answer') and from get_event ('call get_event for the full text of one'), so an agent can tell which tool to pick without opening another schema.

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 concrete when-to-use cases: meeting content, invitees, last meeting with X, private calendar entries, and all-day vacation entries. It also routes full-text retrieval to get_event and states the availability window, leaving little ambiguity about when this tool is appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources