Skip to main content
Glama

Axad

Card review

show_review
Read-only

Displays the learner's due flash cards one at a time: the front, the answer and example on a tap, then four taps to grade the recall, which schedules the card's next review. Needs the learner's account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "show_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoBCP 47 code of the cards' language: "nl" (the default).
nextNoUp to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.
limitNoHow many cards to load, at most 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Beyond the annotations it discloses the interaction sequence, the account requirement, and that grading schedules the next review — useful context the readOnly/openWorld hints do not convey. However, the claim that grading 'schedules the card's next review' sits uneasily with readOnlyHint=true and idempotentHint=false, and the description never clarifies whether that scheduling happens inside this tool or through the review_card sibling.

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?

A single front-loaded sentence that flows from display, to reveal-on-tap, to grading, with no filler. It is information-dense rather than padded, though the long clause chain slightly hurts scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully states what is shown on screen (front, answer, example) and the account prerequisite. The remaining gap is the end-state behavior — what is returned when no cards are due or when loading is capped by limit.

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 description coverage is 100%, so lang, next, and limit are already fully documented in the schema, and the description adds no format or constraint detail for them. The only marginal link is the 'four taps' wording hinting at the next-steps parameter, but it is not made explicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Displays the learner's due flash cards') and details the interaction shape (front, answer/example on tap, four grading taps). It does not differentiate itself from near-name siblings like review_card or due_cards, so an agent must still infer which one actually renders the card.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: use it when the learner has due cards to work through. The prerequisite 'Needs the learner's account' is stated, but there is no explicit when-not guidance or pointer to alternatives such as review_card for submitting a grade or due_cards for listing counts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.