Skip to main content
Glama

Search Events

search_events
Read-onlyIdempotent

Search calendar events by title, location, or description within a specified date range. Returns matching events from your Microsoft calendar.

Instructions

📖 Search calendar events (read-only, safe for unsupervised use)

Searches event titles, locations, and descriptions within date range. Automatically routes to the appropriate API based on account type:

  • Personal accounts: Uses OData $search parameter

  • Work/school accounts: Uses unified search API

Args: query: Search query string (1-512 characters) account_id: Microsoft account ID days_ahead: Days to look forward (0-730, default: 365) days_back: Days to look back (0-730, default: 365) limit: Maximum results to return (1-500, default: 50) use_cache: Whether to use cache (default: True) force_refresh: Bypass cache and fetch fresh data (default: False)

Returns: List of matching events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
account_idYes
days_aheadNo
days_backNo
limitNo
use_cacheNo
force_refreshNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate safety and idempotency. Description adds routing behavior and search scope details. No contradictions; adds meaningful context beyond 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?

Well-structured with emoji summary at top, then details, and a bullet-list of args. Every sentence adds value, no fluff. Front-loaded with key info.

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?

Covers search behavior, routing, and parameter details. Output schema exists, so return description is sufficient. Could mention ordering or pagination, but not necessary for this tool.

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?

Schema has 0% description coverage, but the description includes a full Arg list with constraints (character limits, ranges, defaults), fully compensating for lack of schema descriptions.

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?

Clearly states it's a search tool for calendar events, specifying searched fields (title, location, description) and read-only nature. Differentiated from sibling search tools (contacts, emails, files, unified).

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?

Provides context on automatic API routing based on account type and notes read-only safe use. Lacks explicit when-not-to-use or alternative suggestions, but purpose is clear among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robin-collins/m365-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server