Caly

Disconnect calendar

disconnect_calendar

Destructive

Disconnect a calendar by provider and credential id (both from list_calendars). Two steps: the first call returns CONFIRMATION_REQUIRED with a confirmToken; tell the user what will happen, then call again with the SAME arguments plus confirmToken.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "calendar": "<calendar>",
      "id": "<id>"
    },
    "name": "disconnect_calendar"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The calendar's credentialId.
`calendar`	Yes	Calendar provider id from list_calendars, e.g. google, office365 or apple.
`confirmToken`	No	Leave empty on the first call. Then pass the token from the CONFIRMATION_REQUIRED answer.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark this destructive and non-idempotent, but the description adds behavior the annotations cannot convey: the CONFIRMATION_REQUIRED handshake, the confirmToken requirement, the need to re-send the SAME arguments, and the instruction to inform the user first. It still never says what 'disconnect' actually does to the calendar's credentials or existing events, so the agent must infer the consequence before warning the user.

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?

Two sentences, front-loaded with the identity of the resource and its keys, then the procedural flow. No filler and nothing redundant with the schema.

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 destructive, non-idempotent mutation with no output schema, the description covers inputs, sequencing, and the user-notification duty. The one gap is the effect itself — whether the credential is revoked, events deleted, or bookings affected — which an agent needs in order to fulfill the 'tell the user what will happen' instruction.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real value: it names both parameters as a pair from list_calendars (cross-tool provenance) and stresses that the retry must reuse the SAME arguments, which clarifies confirmToken's relationship to the other two fields beyond the schema's 'leave empty on the first call' note.

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?

States a specific verb and resource ('Disconnect a calendar') plus the two identifying keys (provider + credential id) and where they originate (list_calendars). It is clearly scoped to a single calendar connection, though it does not explicitly distinguish itself from nearby siblings like 'disconnect', 'disconnect_conferencing', or 'disconnect_sign_in_method'.

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?

Gives the prerequisite (both arguments come from list_calendars) and prescribes the call sequence: first call, then a second call with the identical arguments plus the token. It does not state when a user should prefer unselect_calendar or simply leave a calendar connected, so no alternatives are named.

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

All Caly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?