Skip to main content
Glama

List Review Items

list_review_items
Read-only

Lists saved review items with their schedules while hiding answers by default to prevent spoiling retrieval practice; include answers only when checking or editing.

Instructions

Lists saved review items with their schedule, without answers, so browsing the list does not spoil retrieval practice. Set include_answers only when the student wants to edit or check an item.

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": "list_review_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoMatch topics containing this text
course_idNo
include_answersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description adds a genuinely non-obvious behavioral trait: answers are omitted by default specifically so that browsing the list does not spoil retrieval practice. That explains the default's purpose, not just its mechanics. It does not cover return shape, ordering, or pagination, which keeps it below 5.

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, no waste, and the default-behavior constraint is front-loaded before the optional flag. The rationale for the default is delivered in the same clause rather than a separate paragraph.

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 read-only list tool with three optional parameters and no output schema, the description covers purpose, the default answer omission, and the one flag that changes behavior. What is missing is how topic and course_id compose (AND versus override) and whether results are paginated, neither of which is recoverable from the sparse schema.

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 low at 33%, so the description must carry weight, and it does for the most consequential parameter: include_answers is given a rationale and a condition for setting it true. The other two parameters, topic and course_id, are left entirely to the schema, with course_id having no description at all, so filtering semantics are only partly compensated.

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 resource ('Lists saved review items') plus the scope of what is returned ('with their schedule, without answers'), so an agent can tell this is a browse/list operation rather than a retrieval-practice or stats tool. It stops short of naming a sibling it differs from, e.g. get_due_reviews or attempt_review, so differentiation is inferred rather than stated.

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?

Gives conditional guidance for one case: set include_answers only when the student wants to edit or check an item, which implies the default browsing scenario. It offers no when-not guidance and no explicit alternative for viewing due items versus saved items, leaving the choice against get_due_reviews or get_review_stats to inference.

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