Skip to main content
Glama
Sign In
google-calendar-mcp

google-calendar-mcp

by coldinnn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_events

Find calendar events using a keyword search, with adjustable look-ahead days to locate meetings or tasks quickly.

Instructions

Search for calendar events by keyword.

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

NameRequiredDescriptionDefault
queryYesSearch keyword
days_aheadNoHow many days ahead to search

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, yet description fails to disclose behavioral traits like being a read-only operation, or any limitations such as pagination or rate limits. Agent has no indication of side effects.

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?

Single sentence, no wasted words. However, it's arguably too concise, lacking context for a search tool.

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

Completeness3/5

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

Minimal info given; no output schema or annotations. Description doesn't specify return format, pagination, or whether events are filtered by user's calendar. Adequate but missing important context.

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?

Both parameters are fully described in the input schema (100% coverage). Description adds no additional meaning beyond schema, earning baseline score.

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?

Description clearly states verb 'search' and resource 'calendar events' with method 'by keyword'. Distinguishes from siblings like list_events (which may list all without keyword) and create/delete/update events.

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 explicit guidance on when to use this tool versus alternatives like list_events or find_free_time. The description is too vague to help an agent decide between search and list.

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

Deploy Server

Other Tools