Flash

Show answer

show_answer

Read-only

Use this when the user gives up on the card just asked in a study session, or asks for its answer. Returns the card's back and records nothing: tell the user the answer, then call submit_review with rating 1 (Again). To read whole cards outside a session, use list_cards.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`card_id`	Yes	The card whose answer to show: the card_id of the front just asked.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`media`	Yes
`back_html`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026
- addedInput schema / properties / card_id / description
```
Added value: +"The card whose answer to show: the card_id of the front just asked."
```

Changed6 schema fields changedSep 19, 2026

addedOutput schema / $defs

Added value: +{
+  "MediaOut": {
+    "properties": {
+      "filename": {
+        "type": "string"
+      },
+      "media_id": {
+        "format": "int64",
+        "type": "integer"
+      },
+      "mime": {
+        "type": "string"
+      },
+      "size": {
+        "format": "uint64",
+        "minimum": 0,
+        "type": "integer"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "media_id",
+      "url",
+      "mime",
+      "filename",
+      "size"
+    ],
+    "type": "object"
+  }
+}

removedOutput schema / properties / back

Removed value: -{
-  "description": "The card's back (the answer).",
-  "type": "string"
-}

addedOutput schema / properties / back_html
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / media

Added value: +{
+  "items": {
+    "$ref": "#/$defs/MediaOut"
+  },
+  "type": "array"
+}

removedOutput schema / properties / spoken_back

Removed value: -{
-  "description": "The answer as it should be read aloud (a cloze card speaks the\nmissing word here). Speak this rather than `back` when talking.",
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "back",
-  "spoken_back"
-]New value: +[
+  "back_html",
+  "media"
+]

Changed2 schema fields changedSep 17, 2026

addedOutput schema / properties / spoken_back

Added value: +{
+  "description": "The answer as it should be read aloud (a cloze card speaks the\nmissing word here). Speak this rather than `back` when talking.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "back"
-]New value: +[
+  "back",
+  "spoken_back"
+]

First observedSep 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: 'records nothing' clarifies the call has no scheduling side effect, and it supplies the required follow-up workflow (tell the user, then submit_review rating 1). It does not describe what happens if called outside a session, but the coverage is strong.

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 tight sentences: trigger, return/behavior, then alternative. Front-loaded with the use condition and no filler; each sentence carries a distinct instruction.

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 single-parameter read tool with an output schema present, the description need not explain return values, yet it briefly does ('returns the card's back'). Combined with the workflow handoff to submit_review, an agent has everything needed to call it correctly.

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?

Only one parameter with 100% schema description coverage, which already says it is 'the card whose answer to show: the card_id of the front just asked.' The description reinforces the same constraint without adding new syntax or format meaning, so baseline 3 applies.

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 ('show the answer', 'card's back') and pins it to a precise moment: the card just asked in a study session. It also names the sibling it is not (list_cards) for the out-of-session case, so an agent can route correctly without opening schemas.

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?

Explicit triggering conditions ('user gives up', 'asks for its answer'), an explicit exclusion with the alternative ('to read whole cards outside a session, use list_cards'), and a prescribed follow-up action (submit_review with rating 1/Again). Nothing is left to inference.

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.