Flash

Delete deck

delete_deck

Destructive

Use this when the user asks to permanently delete a whole deck, every subdeck under it and all their cards. The first call deletes nothing and returns decks_affected, the affected card IDs and count, and a confirm_token: name every affected deck, ask once, then repeat the same deck with the token. Tokens last ten minutes across reconnects; a changed card or subdeck needs a fresh confirmation. To keep the cards but stop studying them, use archive_deck.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`deck`	Yes	The deck's full name, e.g. "Pharm::Cardio" (list_decks has the names).
`confirm_token`	No	Omit on the first call; pass back the token the first call returned, after the user has confirmed.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`deleted`	Yes
`pending`	Yes
`card_ids`	Yes
`expires_ms`	No
`deck_totals`	Yes
`confirm_token`	No
`cards_affected`	Yes
`decks_affected`	Yes	A deck deletion: the decks that go, by name, the deck first and then the decks under it. Empty for a deletion of cards.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / deck / description

Previous value: -"Deck name."New value: +"The deck's full name, e.g. \"Pharm::Cardio\" (list_decks has the\nnames)."

Changed2 schema fields changedSep 19, 2026

addedOutput schema / properties / decks_affected

Added value: +{
+  "description": "A deck deletion: the decks that go, by name, the deck first and\nthen the decks under it. Empty for a deletion of cards.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "deleted",
-  "pending",
-  "cards_affected",
-  "card_ids",
-  "deck_totals"
-]New value: +[
+  "deleted",
+  "pending",
+  "cards_affected",
+  "card_ids",
+  "decks_affected",
+  "deck_totals"
+]

Changed7 schema fields changedSep 19, 2026

addedOutput schema / properties / card_ids

Added value: +{
+  "items": {
+    "format": "int64",
+    "type": "integer"
+  },
+  "type": "array"
+}

removedOutput schema / properties / cards_affected / description

Removed value: -"Cards this deletion removes (removed, once `deleted` is true)."

addedOutput schema / properties / deck_totals

Added value: +{
+  "items": {
+    "maxItems": 2,
+    "minItems": 2,
+    "prefixItems": [
+      {
+        "format": "int64",
+        "type": "integer"
+      },
+      {
+        "format": "uint32",
+        "minimum": 0,
+        "type": "integer"
+      }
+    ],
+    "type": "array"
+  },
+  "type": "array"
+}

removedOutput schema / properties / deleted / description

Removed value: -"True only after a confirmed call removed the target."

addedOutput schema / properties / expires_ms

Added value: +{
+  "format": "int64",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

removedOutput schema / properties / pending / description

Removed value: -"True when this call recorded the request and is waiting for the\nperson's yes; `confirm_token` is set and nothing was removed."

changedOutput schema / required

Previous value: -[
-  "deleted",
-  "pending",
-  "cards_affected"
-]New value: +[
+  "deleted",
+  "pending",
+  "cards_affected",
+  "card_ids",
+  "deck_totals"
+]

First observedSep 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well past the destructiveHint=true annotation with the actual mechanics: the first call deletes nothing, returns decks_affected plus card IDs/count and a confirm_token, tokens expire in ten minutes and survive reconnects, and a changed subdeck invalidates confirmation. This is exactly the kind of operational detail annotations cannot convey.

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?

Five tight sentences, front-loaded with the destructive scope before the fallback alternative. No filler or restated title text.

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?

Despite an output schema existing, the description still names the salient return fields (decks_affected, card IDs and count, confirm_token), and the two-phase confirmation workflow is fully specified. Nothing an agent needs to call this correctly is missing.

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 to confirm_token: it must come from the first call, be passed back after user confirmation, and it expires. The deck parameter is left to the schema, which already covers it adequately.

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 with explicit scope: 'permanently delete a whole deck, every subdeck under it and all their cards.' An agent can distinguish it from sibling archive_deck without opening either 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?

Gives the trigger condition ('when the user asks to permanently delete a whole deck') and names the alternative alongside its selecting condition: 'To keep the cards but stop studying them, use archive_deck.'

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

All Flash tools Inspect

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.