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

google-calendar-mcp

by coldinnn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_events

Retrieve upcoming Google Calendar events for the next N days, with control over the maximum number of results.

Instructions

List upcoming calendar events for the next N days.

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

Input Schema

NameRequiredDescriptionDefault
days_aheadNoHow many days ahead to look
max_resultsNoMax events to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden; it only mentions 'list upcoming calendar events' but fails to disclose behavioral traits such as read-only nature, authentication requirements, recurrence handling, or output format.

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 a single, front-loaded sentence with no wasted words. It is appropriately sized for the tool's simplicity.

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?

Despite the tool being simple, the description lacks details on return value structure, ordering, or inclusion of all-day events. Without an output schema, more description is needed to fully inform the agent.

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 the description adds little beyond the schema. The phrase 'next N days' restates the purpose but does not provide additional detail on defaults or constraints.

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 clearly states it lists upcoming calendar events for a time period, using a specific verb and resource. However, it does not distinguish itself from sibling tools like search_events or find_free_time.

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

Usage Guidelines3/5

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

The description implies usage for listing upcoming events within N days, but provides no explicit guidance on when not to use it or which alternative tool (e.g., search_events for filtering) is more appropriate.

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