Skip to main content
Glama

Get Due Reviews

get_due_reviews
Read-only

Fetches due review prompts, most overdue first, so an assistant can quiz a student one prompt at a time and record each answer.

Instructions

Returns the review items due now, most overdue first, with prompts only. Ask the student one prompt at a time and wait for their own answer. Do not answer for them or hint at the answer; then call attempt_review with what they said.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
course_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A3.7/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, and the description adds real value on top: the result ordering, that only prompts are returned, and the guardrail against revealing answers. It omits pagination/truncation behavior and whether limit caps the number of prompts surfaced.

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 tight sentences: the first establishes what comes back and in what order, the next two establish the interaction protocol. No repetition, and the most important scoping information is front-loaded.

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?

There is no output schema, so the description carries the return-value burden; it partly does by saying prompts only and ordering them, but it never describes the item fields or whether review item IDs are included for the follow-up attempt_review call. Combined with zero parameter documentation, a calling agent still has gaps to guess at.

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?

Schema description coverage is 0%, so both parameters (limit with default 10 and max 50, and course_id) are undocumented in the schema. The description never mentions either one, so an agent gets no guidance on default result count or on scoping reviews to a single course.

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 ('Returns the review items due now'), plus ordering ('most overdue first') and payload shape ('with prompts only'). It implicitly separates itself from list_review_items by the 'due now' scope, but never names the sibling it is not, so the 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 Guidelines4/5

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

Gives an explicit workflow: ask one prompt at a time, wait for the student's own answer, then call attempt_review with what they said. It also states a prohibition (no answering or hinting), which is strong context. It does not say when to prefer get_review_stats, list_review_items, or get_upcoming_work instead.

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