Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

calendar.calendars.transferOwnership

Transfer a secondary Google Workspace calendar to a new data owner using admin privileges. Requires Manage Calendars access and an active calendar.

Instructions

Transfers a secondary calendar between users within a Google Workspace organization. Requires user authentication with Manage Calendars administrator privilege, and one of the following authorization scopes: - https://www.googleapis.com/auth/calendar - https://www.googleapis.com/auth/calendar.calendars In the request, set useAdminAccess to true. The secondary calendar must be active to be transferred. Transferring disabled or deleted calendars isn't supported [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response 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: clear, delete, get, insert, patch, update.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.
calendarIdYes[URL path segment] Calendar identifier. To retrieve calendar IDs, call the calendarList.list method.
newDataOwnerYes[query parameter] The email address of a user who will become the data owner of the calendar.
useAdminAccessYes[query parameter] When true, the method runs using the user's Google Workspace administrator privileges. The calling user must be a Google Workspace administrator with the Manage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / calendarId / description
      Previous value: -"Calendar identifier. To retrieve calendar IDs, call the calendarList.list method."New value: +"[URL path segment] Calendar identifier. To retrieve calendar IDs, call the calendarList.list method."
    • changedInput schema / properties / newDataOwner / description
      Previous value: -"The email address of a user who will become the data owner of the calendar."New value: +"[query parameter] The email address of a user who will become the data owner of the calendar."
    • changedInput schema / properties / useAdminAccess / description
      Previous value: -"When true, the method runs using the user's Google Workspace administrator privileges. The calling user must be a Google Workspace administrator with the Manage"New value: +"[query parameter] When true, the method runs using the user's Google Workspace administrator privileges. The calling user must be a Google Workspace administrator with the Manage"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the HTTP POST mutation semantics, that the call is refused under --readonly safety profiles, the admin-auth requirement, and the response format. It omits whether the transfer is reversible or what happens to the previous owner's access, which matters for a destructive mutation.

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 core purpose and prerequisites are front-loaded well, but the tail contains templated boilerplate about 'request bodies are built from the typed parameters' and the response resource that repeats schema and is not specific to this tool. It is somewhat overlong for what it adds.

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?

For a no-annotation mutation tool with no output schema, it covers auth, scopes, preconditions, HTTP verb, read-only refusal, and return format — enough for an agent to invoke it correctly. Missing reversibility and post-transfer effects keep it from a 5.

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 coverage is 100%, so the baseline is 3. The description adds one directive beyond the schema (useAdminAccess must be set to true) and explains the body_file/params precedence, but does not clarify calendarId or newDataOwner beyond their schema text.

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

Purpose5/5

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

States a specific verb (transfers) with the resource, direction, and constraint: 'Transfers a secondary calendar between users within a Google Workspace organization.' The action is unmistakably distinct from the same-resource siblings (clear, delete, get, insert, patch, update) named at the end.

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

Usage Guidelines4/5

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

Clearly sets prerequisites — Manage Calendars admin privilege, one of two OAuth scopes, and useAdminAccess=true — plus the precondition that the calendar must be active. It does not explicitly state when to prefer it over alternatives or what to do if prerequisites fail, so it stops short of a 5.

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