Skip to main content
Glama

Schedule account deletion

amber_delete_account
DestructiveIdempotent

Schedule permanent account deletion with a 30-day grace period, immediately blocking memory tools and canceling the PayPal subscription. Reverse within 30 days using the cancellation tool.

Instructions

Schedule permanent account deletion in 30 days. Memory tools are blocked immediately (unlike cancellation, which keeps access until period end). Cancels the PayPal subscription. Reversible within 30 days via amber_cancel_account_deletion.

During the grace period: account management tools (status, export, feedback) remain accessible; memory tools are blocked. After 30 days: all data is permanently deleted.

Requires confirm: true. Returns code: cancelled when false, code: already_scheduled if already pending.

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": {
      "confirm": "<confirm>"
    },
    "name": "amber_delete_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet `true` to proceed, `false` to abort without changes. A STRINGIFIED boolean is also accepted (`"true"` and friends), because some clients JSON-stringify every argument; the published type is `boolean` because that is what a client should send.

Output Schema

NameRequiredDescriptionDefault
statusYesAlways `scheduled`: nothing is deleted at the moment of this call.
messageYesA human-readable summary. Relay it, including the date and the fact that it is reversible until then.
deletion_dateYesWhen the data will actually be destroyed (ISO 8601). Until then `amber_cancel_account_deletion` undoes this completely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Set `true` to proceed, `false` to abort without changes."New value: +"Set `true` to proceed, `false` to abort without changes. A STRINGIFIED boolean is also accepted (`\"true\"` and friends), because some clients JSON-stringify every argument; the published type is `boolean` because that is what a client should send."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "deletion_date": {
      +      "description": "When the data will actually be destroyed (ISO 8601). Until then `amber_cancel_account_deletion` undoes this completely.",
      +      "type": "string"
      +    },
      +    "message": {
      +      "description": "A human-readable summary. Relay it, including the date and the fact that it is reversible until then.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "const": "scheduled",
      +      "description": "Always `scheduled`: nothing is deleted at the moment of this call.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "deletion_date",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / confirm / description
      Previous value: -"Safety gate: must be `true` to proceed. When `false`, the tool returns `code: cancelled` without making any changes — use this to confirm the user's intent before scheduling deletion."New value: +"Set `true` to proceed, `false` to abort without changes."
  3. Changed1 schema field changedv1.1.2
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to confirm account deletion scheduling."New value: +"Safety gate: must be `true` to proceed. When `false`, the tool returns `code: cancelled` without making any changes — use this to confirm the user's intent before scheduling deletion."
  4. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description goes well beyond: 30-day deferral, immediate memory-tool blocking versus continued access to account-management tools, automatic PayPal subscription cancellation, and the specific `already_scheduled` state on repeat calls. That is exactly the behavioral context annotations cannot express (timing, side effects on adjacent subsystems, reversibility window). Nothing here contradicts the destructive/idempotent hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and timeframe, then consequences, then requirements, then return codes — a sensible ordering. Slightly redundant: memory tools being 'blocked immediately' is stated in the first line and restated in the grace-period paragraph, which could be merged.

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 destructive, single-parameter, open-world tool this covers everything an agent needs: irreversible-after-30-days warning, what breaks immediately, what still works, the reversal tool, and expected response codes. An output schema exists, so not enumerating return fields further is fine.

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% and the `confirm` description already covers the boolean and the stringified-boolean edge case, so the description is not required to explain the parameter. It still adds value the schema does not: the concrete return codes `cancelled` (confirm=false) and `already_scheduled`, which tell the agent how to interpret the response rather than the input.

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 — 'Schedule permanent account deletion in 30 days' — and immediately distinguishes it from subscription cancellation ('unlike cancellation, which keeps access until period end') and from its own inverse tool `amber_cancel_account_deletion`. An agent can route correctly 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 Guidelines5/5

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

Explicitly separates this from the two nearest alternatives: subscription cancellation (which preserves access to period end) and `amber_cancel_account_deletion` (the reversal path). It also states the exact precondition (`confirm: true`) and what happens when it is false, so the when/when-not decision is fully determined.

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