Skip to main content
Glama

Due reviews

get_due_reviews
Read-only

Stories the learner practised before that are due again now (spaced repetition), oldest first.

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
limitNoDefault 10, at most 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, so the description's job is to add behavior — and it does: results are limited to previously-practised stories that are due, returned oldest first. That ordering guarantee is real behavioral information not present in the annotations or schema. It does not discuss empty-result behavior or whether the full story payload is returned, keeping it off a 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?

One sentence, front-loaded with the resource definition, then the defining condition and the sort order. No redundant or filler wording; every clause carries information.

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 one-optional-param read tool with annotations covering safety and no output schema, the description tells the agent what qualifies as a result and in what order. What it omits — whether story content or just summaries are returned — is minor for correct invocation.

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

Parameters3/5

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

There is a single optional limit parameter and the schema already documents its default (10) and cap (50) at 100% coverage, so the schema carries the burden. The description adds no ordering-vs-limit interaction or batching guidance beyond what the schema provides; baseline 3.

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?

The description names the resource precisely (stories the learner practised before that are now due again) and adds the spaced-repetition mechanism plus sort order, which lets an agent distinguish this from fetching today's stories. It stops short of explicitly contrasting itself with a sibling such as get_daily_stories, so a 4 rather than a 5.

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?

The concept of 'due again now' implies when to call it (a review queue rather than new or daily content), but there is no explicit when-to-use / when-not-to-use statement and no sibling named as the alternative for non-due content. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources