Skip to main content
Glama

Rate Review

rate_review

Schedules the next spaced review after a recall attempt based on the student's rating, requiring 'again' for wrong or missing answers.

Instructions

Schedules the next review of an item from the student's rating of their recall. The student chooses the rating; if their answer was wrong or missing it must be 'again'. Requires attempt_review first.

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": {
      "item_id": "<item_id>",
      "rating": "<rating>"
    },
    "name": "rate_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingYesagain = could not recall, hard = partly or with real effort, good = correct, easy = instant
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-destructive, closed-world call; the description adds the sequencing dependency on attempt_review and the validation constraint on 'again'. It does not explain what the new schedule looks like or whether re-rating overwrites a prior result, which is the remaining behavioral gap.

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 short sentences, each carrying distinct information: what it does, how to pick the rating, and the prerequisite. The prerequisite is placed last where it reads as a gating condition, with no filler.

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 two-parameter mutation with no output schema and annotations already covering the safety profile, the definition supplies the action, the prerequisite, and the rating rule — everything needed to invoke it correctly. Return behavior is not described, but the call semantics are complete.

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 50% — only 'rating' is documented. The description compensates by adding the selection rule and the mandatory-'again' constraint that the enum description alone does not convey. 'item_id' remains unexplained, but its meaning is fairly evident from the review context.

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?

States a specific verb and effect ('Schedules the next review of an item') plus the input that drives it ('from the student's rating of their recall'), which distinguishes it from attempt_review and the item-management siblings. It stops short of naming how the schedule is computed, but the action is unmistakable.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite ('Requires attempt_review first') and a rule for choosing the rating ('if their answer was wrong or missing it must be again'). It does not state what to do if a review was already rated, but the primary when-to-use condition is clear.

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