grr

Overview Schema Source Related Servers Discussions Admin

calendar.calendarList.get

Retrieve a specific calendar from the user's calendar list by calendar ID. Returns calendar details as JSON for viewing or further processing.

Instructions

Returns a calendar from the user's calendar list [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: delete, insert, list, patch, update, watch.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`calendarId`	Yes	[URL path segment] Calendar identifier. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the currently logged in user, use

Output Schema

Name	Required	Description	Default
`id`	No
`etag`	No
`kind`	No
`hidden`	No
`colorId`	No
`deleted`	No
`primary`	No
`summary`	No
`location`	No
`selected`	No
`timeZone`	No
`dataOwner`	No
`accessRole`	No
`description`	No
`backgroundColor`	No
`foregroundColor`	No
`summaryOverride`	No
`defaultReminders`	No
`conferenceProperties`	No
`notificationSettings`	No
`autoAcceptInvitations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / calendarId / description

Previous value: -"Calendar identifier. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the currently logged in user, use"New value: +"[URL path segment] Calendar identifier. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the currently logged in user, use"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accessRole": {
+      "type": "string"
+    },
+    "autoAcceptInvitations": {
+      "type": "boolean"
+    },
+    "backgroundColor": {
+      "type": "string"
+    },
+    "colorId": {
+      "type": "string"
+    },
+    "conferenceProperties": {
+      "properties": {
+        "allowedConferenceSolutionTypes": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "dataOwner": {
+      "type": "string"
+    },
+    "defaultReminders": {
+      "items": {
+        "properties": {
+          "method": {
+            "type": "string"
+          },
+          "minutes": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "deleted": {
+      "type": "boolean"
+    },
+    "description": {
+      "type": "string"
+    },
+    "etag": {
+      "type": "string"
+    },
+    "foregroundColor": {
+      "type": "string"
+    },
+    "hidden": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "notificationSettings": {
+      "properties": {
+        "notifications": {
+          "items": {
+            "properties": {
+              "method": {
+                "type": "string"
+              },
+              "type": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "primary": {
+      "type": "boolean"
+    },
+    "selected": {
+      "type": "boolean"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "summaryOverride": {
+      "type": "string"
+    },
+    "timeZone": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the HTTP GET verb and that the resource is returned as JSON, which implies a read-only operation, but the long clause about request bodies built from typed parameters or body_file is boilerplate that is irrelevant (and mildly confusing) for a GET. Nothing is said about permissions or access scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded, but the second sentence is generic scaffolding about body construction that earns no place in a read-only GET definition. The sibling list is terse to the point of being a name dump.

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?

An output schema exists, so return-value detail is not required, and the GET semantics plus sibling context cover the essentials for invoking it. The remaining gap is guidance on when this is preferable to calendar.calendars.get and clarity around calendarId lookup.

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 baseline is 3. The description adds no meaning beyond the schema for calendarId, and notably the schema's own calendarId description is truncated mid-sentence, which the description does not compensate for.

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?

Opens with a specific verb and resource ('Returns a calendar from the user's calendar list') and names the sibling operations over the same resource, which helps distinguish it from list/delete/update. It does not, however, differentiate itself from the much closer sibling calendar.calendars.get, so the purpose boundary is only partly drawn.

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?

There is no statement of when to use this tool versus alternatives — only a bare enumeration of sibling names with no conditions attached. An agent still has to guess whether it wants calendarList.get or calendars.get, and no prerequisites or exclusions are given.

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

Deploy Server