Skip to main content
Glama

Revoke calendar login

revokeCalendarLogin
Destructive

Revoke one calendar sign-in so the calendar and contacts apps using it are signed out within minutes. The calendars and contacts stay. Another member's needs the workspace owner or a role that manages members.

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": {
      "login": "<login>"
    },
    "name": "revokeCalendarLogin"
  }
}

Input Schema

NameRequiredDescriptionDefault
loginYesThe ID listCalendarLogins shows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as destructive, and the description adds useful context: affected apps are signed out within minutes, calendars and contacts remain, and revoking another member's login requires owner or member-management permissions. It stops short of stating reversibility or full session semantics.

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?

The description is front-loaded, short, and each sentence contributes useful information: the action, the persistence of related data, and the permission caveat. There is no redundant or filler text.

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 simple destructive mutation with full schema coverage and annotations, the description supplies the key impact and permission details. It could be slightly more complete by clarifying reversibility or whether a user can revoke their own login, but it is sufficient for correct invocation.

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 schema already explains that login is the ID from listCalendarLogins. The description adds no additional syntax, format, or constraints beyond the schema baseline.

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?

The description states a specific verb and resource: revoking one calendar sign-in. It also explains the immediate effect on calendar and contacts apps and clarifies that the calendars and contacts themselves remain.

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 the action and effect, and it notes the permission requirement for revoking another member's login. However, it does not explicitly say when to use this versus related revoke tools such as revokeSession or revokeConnectedApp.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.