Skip to main content
Glama

revisions_due

Read-onlyIdempotent

Retrieves practice problems due for spaced-repetition revision, prioritizing those you are least likely to recall so you review weak concepts on schedule.

Instructions

Problems due for revision now, the one the user is least likely to recall 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": "revisions_due"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.0
    • addedOutput schema / $defs / ReviewCard / properties / difficulty
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Difficulty"
      +}
    • changedOutput schema / $defs / ReviewCard / properties / due / format
      Previous value: -"date"New value: +"date-time"
    • removedOutput schema / $defs / ReviewCard / properties / ease
      Removed value: -{
      -  "title": "Ease",
      -  "type": "number"
      -}
    • removedOutput schema / $defs / ReviewCard / properties / interval_days
      Removed value: -{
      -  "title": "Interval Days",
      -  "type": "integer"
      -}
    • removedOutput schema / $defs / ReviewCard / properties / repetitions
      Removed value: -{
      -  "title": "Repetitions",
      -  "type": "integer"
      -}
    • addedOutput schema / $defs / ReviewCard / properties / retrievability
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Retrievability"
      +}
    • addedOutput schema / $defs / ReviewCard / properties / reviews
      Added value: +{
      +  "default": 0,
      +  "title": "Reviews",
      +  "type": "integer"
      +}
    • addedOutput schema / $defs / ReviewCard / properties / stability
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Stability"
      +}
    • changedOutput schema / $defs / ReviewCard / required
      Previous value: -[
      -  "platform",
      -  "problem_id",
      -  "title",
      -  "url",
      -  "ease",
      -  "interval_days",
      -  "repetitions",
      -  "due"
      -]New value: +[
      +  "platform",
      +  "problem_id",
      +  "title",
      +  "url",
      +  "due"
      +]
  2. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one behavioral trait beyond that — an ordering based on likelihood of recall — which is genuinely useful but too vaguely worded to act on, and it says nothing about the default cap of 10 or the maximum of 100.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with the purpose front-loaded, which is the right shape. However, the second clause is confusing rather than informative, so the brevity comes partly at the cost of clarity.

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?

This is a simple read-only tool with annotations and an output schema, so return values need no explanation. Still, the two things an agent actually needs — what the ordering means in practice and what limit controls — are missing or garbled.

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?

The single parameter (limit) has 0% schema description coverage, so the description is the only place its meaning could be established — and it never mentions it. The phrase "the one ... first" hints at ordering/priority but gives no clue that the result set is size-limited or what the default is.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Problems due for revision now" identifies the resource clearly enough, but there is no verb (list/get/fetch) and the trailing clause "the one the user is least likely to recall first" is grammatically tangled and reads more like a sort order than a purpose. An agent can guess this returns due revision items, but the sentence never cleanly states what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives. Siblings such as list_mistakes, search_problems, and log_review are not referenced, so the agent must infer that this is the retrieval step preceding log_review rather than a filtered search.

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