Skip to main content
Glama

Upcoming calendar events

calendar_upcoming
Read-onlyIdempotent

List upcoming Google Calendar events for a specified number of days (default two weeks) to help you plan around scheduled commitments.

Instructions

List Google Calendar events for the next days days (default 2 weeks).

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is fully covered without description help. The description adds only the default window, which duplicates the schema default of 14, and says nothing about time zone, calendar scoping, or ordering of results.

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?

A single front-loaded sentence with the resource and scope stated first and the default appended. Nothing is wasted and nothing is buried.

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?

The tool is simple, the output schema covers return values, and annotations cover safety, so the description need not say more about results. Minor gaps remain around whose calendar/which calendars are read and event ordering, but these are small for a one-parameter listing tool.

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?

With only one parameter at 0% schema description coverage, the description carries the burden and does explain that `days` is a forward-looking day count with a two-week default. That adds real meaning beyond the bare integer default in the schema, though it does not say what happens with 0, negative, or very large values.

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 gives a specific verb ('List') and resource ('Google Calendar events') plus the time window, which distinguishes it from the write-oriented sibling add_to_calendar. It stops short of naming a sibling explicitly, but the read-only listing purpose is unambiguous.

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?

Usage is implied by 'upcoming' and the default window, so an agent can infer this is the tool for forward-looking event retrieval. There is no explicit when-to-use statement, no exclusion such as past events, and no reference to alternatives like add_to_calendar for writes.

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