Skip to main content
Glama
LeetCode Tracker MCP

LeetCode Tracker MCP

by aleprime-gh

get_problem_history

Read-only

Retrieve a single LeetCode problem's details, attempts, notes, and review schedule by slug or URL to track progress and plan spaced-repetition reviews.

Instructions

Show one problem's details, attempts, notes and review schedule.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "problem": "<problem>"
    },
    "name": "get_problem_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
problemYesProblem slug or URL, for example two-sum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description's main added value is enumerating the returned sections. It does not mention that the problem is resolved from an external source (openWorld) and what happens for an unknown slug, nor any latency or failure behavior.

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 front-loaded sentence with zero filler; every phrase names a distinct piece of returned content.

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?

For a one-parameter read tool with no output schema, listing the returned sections is genuinely useful. However, with openWorldHint=true there is unexplained external-resolution behavior, and no guidance on resolving an invalid slug or on how this differs from the progress/review siblings.

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 coverage is 100% and the single parameter already documents that it accepts a slug or URL with an example ('two-sum'). The description adds nothing about the identifier format, so the baseline 3 is appropriate.

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 uses a specific verb ('Show') plus a singular resource ('one problem's details') and enumerates the payload sections: details, attempts, notes, review schedule. The singular framing implicitly separates it from list-shaped siblings like list_tracked_problems, but it never names a sibling to contrast against, 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. An agent reading this cannot tell whether to call it instead of get_progress, get_due_reviews, or list_tracked_problems for problem-related questions; the only usable cue is that it takes a single problem identifier.

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