Skip to main content
Glama

Add Review Items

add_review_items

Adds question-and-answer items to a student's local spaced-review schedule so they can start reviewing course material right away.

Instructions

Saves question-and-answer items to the student's spaced-review schedule, stored only on their computer. Prefer items the student wrote in their own words; draft items yourself only when asked, and show them to the student first. A good item covers one idea, asks why or how rather than for a bare definition, and can be answered in a sentence or two. New items are due right away.

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": {
      "items": "<items>"
    },
    "name": "add_review_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
course_idNo
course_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only, non-destructive, local operation. The description adds useful behavioral context: items are stored only on the student's computer and new items are due right away. It does not discuss duplicate handling, limits, or response behavior, but it goes beyond the annotations in meaningful ways.

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?

The description is short, front-loaded, and every sentence adds useful information. Purpose, sourcing guidance, item quality criteria, and immediate due-date behavior are all presented without filler.

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

Completeness3/5

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

For a simple create-style tool with no output schema, the description covers the purpose, content expectations, local storage, and immediate scheduling well. However, it omits any explanation of the course_id and course_name parameters, which is a notable gap given the reported 0% schema description coverage for those top-level fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage reported at 0%, the description should compensate for undocumented parameters, but it never mentions course_id or course_name. It gives useful content guidance for the items themselves, including the student-versus-assistant authorship distinction, but it does not explain parameter roles or formatting.

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?

The description states a specific verb and resource: it saves question-and-answer items to the student's spaced-review schedule. It also clarifies that the storage is local to the student's computer and that new items are immediately due. This is sufficiently distinct from sibling tools such as list_review_items, update_review_item, and attempt_review.

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?

The description gives clear guidance on what to add: prefer items the student wrote themselves, and only draft items when asked, showing drafts to the student first. It does not explicitly contrast this tool with alternatives like update_review_item, but the intended use case for adding new items is clear.

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