Flash

Study panel: show answer

panel_show_answer

Read-only

Used by Flash's study panel only; never call it yourself (use show_answer). Returns a card's back for the panel.

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
`card_id`	Yes
`back_html`	Yes
`back_lang`	No	The back's language, for its `lang`; absent when nothing says it.
`comes_back_in_ms`	No	How long until the card comes back after each grade, Again, Hard, Good, Easy, in ms: what the grade buttons say.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

addedOutput schema / properties / back_lang

Added value: +{
+  "description": "The back's language, for its `lang`; absent when nothing says it.",
+  "type": "string"
+}

Changed2 schema fields 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."

addedOutput schema / properties / comes_back_in_ms

Added value: +{
+  "description": "How long until the card comes back after each grade, Again, Hard,\nGood, Easy, in ms: what the grade buttons say.",
+  "items": {
+    "format": "int64",
+    "type": "integer"
+  },
+  "maxItems": 4,
+  "minItems": 4,
+  "type": [
+    "array",
+    "null"
+  ]
+}

AddedSep 27, 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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: the tool is an internal panel-only endpoint, which is a behavioral constraint no annotation expresses. It does not cover return shape or latency, but the output schema carries returns.

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?

Two short sentences, zero waste, with the caller restriction front-loaded ahead of the return description. Every clause carries information an agent needs.

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?

An output schema exists, so return values need not be explained. Given that, the description covers the only non-obvious thing about this tool: who is allowed to invoke it and what to call instead.

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?

Schema coverage is 100% and card_id is fully documented there ('the card_id of the front just asked'), so the schema does the heavy lifting. The description adds no parameter syntax or semantics beyond that, making the baseline 3 correct.

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 ('Returns a card's back') and immediately scopes it to the study panel, which is exactly what distinguishes it from the sibling show_answer. An agent can route between the two 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?

Explicitly says 'never call it yourself' and names the alternative to use instead ('use show_answer'). This is a rare case of a tool that positively documents when NOT to call it, with the substitute named.

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.