Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

calendar.calendars.delete

Deletes a secondary calendar by ID, permanently removing it from the account. Use clear instead to remove events from a primary calendar.

Instructions

Deletes a secondary calendar. Use calendars.clear for clearing all events on primary calendars [HTTP DELETE] — removes the resource; irreversible unless the API documents a trash/undo flow; refused under --readonly safety profiles. Returns the post-delete resource state (or empty) 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, get, insert, patch, transferOwnership, 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. If you want to access the primary calendar of the currently logged in user, use

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations, so the description carries the full load, and it does disclose the important traits: HTTP DELETE semantics, irreversibility absent a trash/undo flow, refusal under --readonly safety profiles, and the post-delete return value. It omits permission/ownership requirements for deleting a secondary calendar, which is the main residual gap.

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 two sentences are tight and front-loaded, but the trailing explanation of request-body construction (typed flags vs params map, body_file) is generic boilerplate that is irrelevant for a DELETE with no body. Sibling enumeration at the end is useful but long.

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?

With no annotations and no output schema, the description correctly fills the gap by naming the return value (post-delete resource state or empty JSON) and the irreversibility risk. Missing auth/ownership prerequisites and the primary-vs-secondary constraint on calendarId keep it short of complete.

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 calendarId, query, params, dry_run and body_file are all documented structurally; the description only restates the typed-params-beat-params-map and body_file precedence. That restatement is useful precedence context but adds nothing specific about calendarId semantics.

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 and resource ("Deletes a secondary calendar") and immediately scopes it against the closest sibling by explaining that clearing events is calendars.clear's job. An agent can pick between delete and clear without opening either schema.

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?

Explicitly names the alternative (calendars.clear) and the condition that selects it (primary calendars / clearing events rather than removing the calendar). It does not, however, disambiguate against calendar.calendarList.delete, which is a real sibling that also removes a calendar from a list — a likely point of confusion.

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