Skip to main content
Glama
Sign In

Caly

by com.trycaly
OverviewDiscussionsAdmin

Disconnect sign-in method

disconnect_sign_in_method
Destructive

Remove Google or Apple as a way to sign in to the user's Caly account. The last remaining way in can never be removed, so the call is refused (sign_in_method_last_method) if it is the only one; a method that is not connected is refused too (sign_in_method_not_connected_error). Check list_sign_in_methods first. The password is changed with change_password, and to add a password before removing the only Google or Apple sign-in, use send_password_setup_email. Connecting Google or Apple is done by the user on the Caly website, in the Security section of their account settings. 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": {
      "provider": "<provider>"
    },
    "name": "disconnect_sign_in_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesThe sign-in method to remove.
confirmTokenNoLeave empty on the first call. Then pass the token from the CONFIRMATION_REQUIRED answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructive/openWorld annotations, it discloses the last-method invariant and the specific error codes returned (sign_in_method_last_method, sign_in_method_not_connected_error), plus the full two-step confirmation protocol with CONFIRMATION_REQUIRED and confirmToken. This is exactly the behavioral context annotations cannot carry.

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?

Front-loads the action, then the constraints, then the alternatives, then the confirmation flow. Dense but every sentence carries operational value; nothing is restated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the relevant return behaviors (error codes, CONFIRMATION_REQUIRED token) and the prerequisites. An agent has everything needed to invoke correctly and to avoid the last-method failure.

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 meaning about confirmToken: it is issued by the first call and must be re-sent with the SAME arguments on the retry. That operational detail is not in the 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 and resource ('Remove Google or Apple as a way to sign in to the user's Caly account'), scoping it to sign-in methods rather than calendars or conferencing. This clearly separates it from siblings like disconnect, disconnect_calendar, and disconnect_conferencing.

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

Usage Guidelines5/5

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

Explicitly tells the agent to call list_sign_in_methods first, routes password changes to change_password and password setup to send_password_setup_email, and notes that connecting a method happens on the website (i.e., not via a tool). This is close to a complete decision tree.

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

All Caly toolsInspect
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