Skip to main content
Glama

Attempt Review

attempt_review

Records the student's exact answer to a review prompt, returns the reference answer, compares the two honestly, and prompts a recall rating.

Instructions

Records the student's own answer to a review prompt and returns the reference answer. Pass what the student actually said, word for word, including 'I don't know'. Never invent or improve their answer. Then compare the two for them honestly and ask them to rate their recall with rate_review.

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>",
      "student_answer": "<student_answer>"
    },
    "name": "attempt_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
student_answerYesThe student's answer in their own words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description adds substantive behavior beyond that: the tool persists the answer (consistent with the non-read-only hint) and returns the reference answer, which matters because there is no output schema. It also constrains agent behavior by forbidding invention or improvement of the student's answer. It does not state what happens on repeated attempts for the same item or how the comparison is surfaced.

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?

Purpose is front-loaded in the first sentence, followed by actionable instructions in short imperative sentences. Every sentence carries weight, though the clause 'Then compare the two for them honestly' is slightly ambiguous about whether the tool or the agent performs that comparison.

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 only two parameters, no output schema, and no nested objects, the description does the heavy lifting expected of it: it explains what is returned (the reference answer) and what comes next (rate_review). The main remaining gap is what item_id refers to and where the agent obtains it, plus the ambiguity over who produces the comparison.

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%: student_answer has a description, item_id does not. The description compensates strongly for student_answer by mandating verbatim text and explicitly allowing 'I don't know', which goes well beyond the schema's 'in their own words'. item_id remains unexplained in both schema and description, so it is not a full 5.

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+resource pair: records the student's own answer to a review prompt and returns the reference answer. It also names the sibling it hands off to (rate_review), so the agent can distinguish this step from the rest of the review flow without opening any schema.

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 clear context for invocation: call it with the student's verbatim answer, then proceed to rate_review. There is explicit sequencing guidance but no explicit when-not-to-use or exclusion against the other review siblings such as update_review_item or add_review_items.

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