google-workspace-alias-mcp

search_events

Search calendar events using a query, start and end times, and limit results. Retrieve events matching keywords within a specified time period.

Instructions

Search calendar events

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_events"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query
`timeMax`	No	End time (ISO format)
`timeMin`	No	Start time (ISO format)
`calendarId`	No	Calendar ID	primary
`maxResults`	No	Maximum number of results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must convey behavioral traits. It only says 'search', implying read-only, but does not disclose return format, pagination, or other constraints.

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?

The description is very concise at four words, front-loading the key information. However, it sacrifices detail for brevity, lacking structure for complex behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has five parameters and no output schema, the description is too brief to be complete. It fails to explain return values, behavior, or nuances.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search calendar events' clearly states the action (search) on the resource (calendar events). However, it does not differentiate from sibling tools like list_events or get_event, which might have similar purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use search_events versus alternatives like list_events. The description lacks context for usage scenarios or exclusions.

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