Skip to main content
Glama

Cancel scheduled account deletion

amber_cancel_account_deletion
Idempotent

Cancel a scheduled account deletion to remove the pending deadline and restore access to memory tools immediately, without losing any data.

Instructions

Cancel a previously scheduled account deletion. Removes the deletion deadline and unblocks memory tools immediately. Access resumes until next_billing_date (the remaining paid period). No data is lost.

Side effects: clears deletion_scheduled_at from the account. The PayPal subscription was already cancelled when deletion was scheduled -- call amber_reactivate_subscription to start a new one if the paid period has expired. Returns code: not_scheduled if no deletion is pending. Not rate-limited.

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": "amber_cancel_account_deletion"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusYesAlways `cancelled`: the scheduled deletion is off and the account is fully intact. Nothing had been destroyed while it was pending.
messageYesA human-readable confirmation to relay to the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "message": {
      +      "description": "A human-readable confirmation to relay to the user.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "const": "cancelled",
      +      "description": "Always `cancelled`: the scheduled deletion is off and the account is fully intact. Nothing had been destroyed while it was pending.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only give the generic safety profile (readOnly=false, idempotent=true, destructive=false); the description goes far beyond that with concrete effects: unblocking memory tools immediately, access only until next_billing_date, no data loss, clearing deletion_scheduled_at, and the prior cancellation of the PayPal subscription. It even discloses the 'not_scheduled' error code and confirms no rate limiting, which annotations cannot express.

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 outcome and immediate effect are front-loaded, followed by a clearly labeled 'Side effects' block and an error-case sentence. Every sentence carries actionable information, including the subscription-reactivation pointer and the error code, with no filler.

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?

For a zero-argument state-changing tool with an output schema already covering return values, the description supplies the missing pieces an agent needs: what state is cleared, what access resumes, what the billing consequence is, and the failure mode. Nothing material is left to inference.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param tool is a 4. The description correctly avoids inventing parameter talk and instead spends its words on behavior.

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 first sentence names a specific verb and resource ('Cancel a previously scheduled account deletion'), which cleanly distinguishes it from siblings like amber_delete_account (irreversible) and amber_cancel_subscription (billing only). An agent can route between these without opening any 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?

The description establishes the precondition (a deletion must be pending) and the alternative path when the paid period has expired ('call amber_reactivate_subscription to start a new one'). It does not explicitly say when not to use it versus amber_delete_account, but the conditional guidance is clear enough for confident selection.

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