Skip to main content
Glama
Sign In

Caly

by com.trycaly
OverviewDiscussionsAdmin

Delete account

delete_account
Destructive

Delete the user's Caly account. It is locked immediately (sign-in and this connection stop working) and permanently removed after 30 days; support can restore it until then. Caly cancels plans it bills itself; when the result has cancelInStore, show that text to the user (an App Store or Google Play subscription they must cancel in the store). Two steps: the first call returns CONFIRMATION_REQUIRED with a confirmToken; tell the user the consequences, then call again with the SAME arguments plus confirmToken.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes far beyond them: immediate lockout, loss of sign-in and this connection, 30-day recovery window via support, and which plans Caly cancels itself. This is exactly the operational context an agent needs before a destructive, non-idempotent call.

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?

Three dense sentences with the consequence and the lockout timeline front-loaded, followed by the billing edge case and the two-step procedure. No filler, and the ordering matches how an agent must act.

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?

No output schema exists, yet the description explains the two relevant response shapes (CONFIRMATION_REQUIRED with confirmToken, and a result carrying cancelInStore text). Combined with the destructive annotations, an agent has everything needed to call it safely.

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% and the schema already documents confirmToken's first-call/second-call semantics, so the description largely restates it rather than adding new meaning. Baseline 3 is correct for a single fully documented parameter.

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 ("Delete the user's Caly account") and immediately scopes it to the account itself, distinguishing it from sibling destructive tools like delete_organization, delete_team, or delete_webhook.

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?

Gives an explicit sequence: first call returns CONFIRMATION_REQUIRED with a confirmToken, tell the user the consequences, then call again with identical arguments plus the token. It also names the conditional path for cancelInStore subscriptions that must be handled in the App Store or Google Play.

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