Skip to main content
Glama
LeetCode Tracker MCP

LeetCode Tracker MCP

by aleprime-gh

list_tracked_problems

Read-only

Retrieves locally tracked LeetCode problems, most recently attempted first, with optional filters for topic, status, difficulty, and result limit.

Instructions

List locally tracked problems, most recently attempted 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": "list_tracked_problems"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefaults to 50.
topicNoTopic slug or name, for example dynamic-programming.
statusNo
difficultyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful ordering context with "most recently attempted first," but it does not explain pagination, what fields are returned, or what "locally tracked" means operationally.

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?

It is a single, front-loaded sentence with no wasted wording. The resource and ordering hint are both conveyed efficiently.

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 simple read-only list tool, the description plus annotations and schema are minimally adequate. However, with no output schema, the definition should say more about what is returned or how filtering and result limits behave.

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 schema describes the limit and topic parameters and defines enums for status and difficulty, but description coverage is only 50%. The description adds no parameter meaning beyond the schema and does not compensate for the undocumented enum semantics.

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 states a specific verb and resource: "List locally tracked problems," and adds the ordering behavior "most recently attempted first." It does not explicitly distinguish this from sibling tools such as get_problem_history or get_progress, but the core purpose is clear.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. It implies this is for listing locally tracked problems, but an agent gets no help deciding between this and get_problem_history or get_progress.

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