Flash

create_cards

Use to add flashcards the user asks for, from their notes, a document, a topic or this conversation. Creates 1-500 cards in one deck (created if missing, with its parents when named Parent::Child), atomically. Follow the field notes to write cards worth learning from. Cloze uses {{c1::answer}}. Keep media references as /media/{id} (IDs from list_cards). To fix cards that exist, use update_cards rather than adding copies. Returns the card IDs and counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`deck`	Yes
`cards`	Yes	On both sides keep the material's own terms, names and numbers. Write what plain text loses as HTML (10<sup>5</sup>, not 105; H<sub>2</sub>O; <br> between lines), and write each text in one script, as the material or the user writes it, never switching alphabets inside a word.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`created`	Yes
`updated`	Yes
`card_ids`	Yes
`source_ids`	Yes
`deck_totals`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 27, 2026

addedInput schema / $defs / NewCard / properties / back_html / description

Added value: +"The answer to exactly what the front asks, as short as it can be while complete. Anything more (why, an example, a source) comes after the answer, set apart."

addedInput schema / $defs / NewCard / properties / front_html / description

Added value: +"The prompt, answerable on its own: one question, cue or cloze sentence carrying everything needed to answer it (the choices of a multiple-choice question, the context a case depends on). One idea per card: a list, a multi-part rule or a comparison becomes several cards, or a cloze with one blank per part."

addedInput schema / $defs / NewCard / properties / note_type / description

Added value: +"basic (default): one question, one answer. basic_reversed: both directions are worth asking (a word and its translation, a term and its definition). basic_typed: the exact spelling, number or formula matters. cloze: a sentence whose blanks are each their own fact, {{c1::...}}, {{c2::...}}."

addedInput schema / $defs / NewCard / properties / tags / description

Added value: +"A few short lowercase topic words (a chapter, a lesson, a theme), so the user can study one part later."

addedInput schema / properties / cards / description

Added value: +"On both sides keep the material's own terms, names and numbers. Write what plain text loses as HTML (10<sup>5</sup>, not 105; H<sub>2</sub>O; <br> between lines), and write each text in one script, as the material or the user writes it, never switching alphabets inside a word."

Changed18 schema fields changedSep 19, 2026

addedInput schema / $defs / NewCard / additionalProperties
```
Added value: +false
```
removedInput schema / $defs / NewCard / properties / back
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / $defs / NewCard / properties / back_html
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / $defs / NewCard / properties / front
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / $defs / NewCard / properties / front_html
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / $defs / NewCard / properties / note_type

Added value: +{
+  "default": null,
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedInput schema / $defs / NewCard / properties / tags / default
```
Previous value: -nullNew value: +[]
```
removedInput schema / $defs / NewCard / properties / tags / description
```
Removed value: -"Optional tags, e.g. [\"exam-2\", \"cardiac\"]"
```

changedInput schema / $defs / NewCard / properties / tags / type

Previous value: -[
-  "array",
-  "null"
-]New value: +"array"

changedInput schema / $defs / NewCard / required

Previous value: -[
-  "front",
-  "back"
-]New value: +[
+  "front_html",
+  "back_html"
+]

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / deck / description

Removed value: -"Target deck; created if it doesn't exist."

addedOutput schema / properties / card_ids

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

removedOutput schema / properties / created / description
```
Removed value: -"Number of cards created."
```

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"
+}

addedOutput schema / properties / source_ids

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

addedOutput schema / properties / updated

Added value: +{
+  "format": "uint32",
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "created"
-]New value: +[
+  "source_ids",
+  "card_ids",
+  "created",
+  "updated",
+  "deck_totals"
+]

First observedSep 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover the safe-mutation profile. The description adds real behavioral facts beyond them: atomic creation, the 1-500 card bound, auto-creation of a missing deck including named Parent::Child ancestors, and the media reference convention. These are exactly the traits an agent needs before calling.

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 purpose and constraints, and every sentence carries operational information. The only slightly soft line is the meta-instruction to 'follow the field notes,' which is generic, but it costs little.

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?

Deck auto-creation, hierarchy syntax, atomicity, card limits, media conventions, and sibling routing are all covered, and an output schema already exists so return values need not be explained. Nothing needed to invoke 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 only 50%, so the description must compensate and largely does: it explains deck hierarchy syntax (Parent::Child) for the undocumented deck parameter and gives cloze syntax ({{c1::answer}}) and media handling for the card payload. It stops short of fully documenting the card fields, which the schema itself handles.

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 (add flashcards) plus the accepted sources (notes, document, topic, conversation), and explicitly distinguishes itself from update_cards. An agent can tell it apart from every sibling without opening a 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 both when-to-use (the user asks for cards, from these sources) and an explicit alternative (use update_cards to fix cards that exist rather than adding copies). The routing condition is unambiguous.

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.