Skip to main content
Glama
LeetCode Tracker MCP

LeetCode Tracker MCP

by aleprime-gh

get_due_reviews

Read-only

Lists LeetCode problems due for spaced-repetition review, ordered most overdue first, with optional upcoming reviews so you can plan study sessions.

Instructions

List problems due for spaced-repetition review, most overdue 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
limitNoDefaults to 10.
upcoming_daysNoAlso show reviews due within this many days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the sort order, which is genuinely useful beyond the annotations, but says nothing about pagination, truncation at the limit, or how the upcoming window changes results.

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?

A single short sentence with the resource and the ordering front-loaded; no filler or redundancy.

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 two-optional-parameter read-only list tool with full schema coverage and no output schema, the description covers the essentials. Only marginal gaps remain around result size behavior and the meaning of the upcoming window.

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?

Schema description coverage is 100%, so both limit (default 10, max 100) and upcoming_days (0-90) are already documented in the schema. The description adds no extra meaning about how upcoming_days interacts with the "most overdue first" ordering, so the baseline of 3 applies.

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 ("List") and resource ("problems due for spaced-repetition review") plus a deterministic ordering ("most overdue first"). An agent knows exactly what comes back, though it does not contrast itself with sibling tools like get_problem_history or list_tracked_problems.

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?

Usage is implied by the phrase "due for spaced-repetition review" – call it when you need today's review queue. There is no explicit when-not guidance or pointer to an alternative for browsing non-due problems.

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