Skip to main content
Glama

Axad

Record a review

review_card

Record how well the learner recalled a card: 1 forgot, 2 hard, 3 good, 4 easy. Schedules the card's next review (FSRS) and returns its due date.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "card": "<card>",
      "grade": "<grade>"
    },
    "name": "review_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYes
gradeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations mark it non-read-only and non-idempotent; the description goes further by disclosing the actual side effect (an FSRS reschedule of the card's next review) and that a due date is returned. That is real behavioral context an agent cannot get from the annotations, though it doesn't say what happens to review history or whether regrading the same card is safe.

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 sentences, front-loaded with the action and the grade semantics, then the side effect and return value. No padding or repetition of the title.

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?

For a two-parameter mutation with no output schema, the description covers the side effect and the returned value, which is the main thing an agent needs. The remaining gap is the identity/format of the card parameter, which the description never addresses.

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 0% and the schema only bounds grade to 1–4, so the description's mapping (1 forgot, 2 hard, 3 good, 4 easy) is essential added meaning for one of two parameters. The other parameter, card, is left completely unexplained – no hint whether it is an ID, slug, or handle – so half the surface remains undocumented.

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?

Specific verb plus resource ("Record how well the learner recalled a card") and the grade scale is spelled out, so the action is unmistakable. It does not compare itself to a sibling (e.g. record_step) or state which card identifiers are acceptable, which keeps it from a 5.

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?

The phrase "how well the learner recalled a card" implies the moment to call it (immediately after a recall attempt), but there are no explicit when-to-use/when-not conditions and no named alternative for other record types. Usage is inferable rather than stated.

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.