Skip to main content
Glama
LeetCode Tracker MCP

LeetCode Tracker MCP

by aleprime-gh

get_progress

Read-only

Retrieve LeetCode progress data—solved counts by difficulty, ranking, streaks, recent activity, weekly/monthly gains, goals, and due reviews—to track performance and plan next study steps.

Instructions

Show solved counts by difficulty, ranking, streak, recent activity, weekly and monthly gains, goals and due reviews.

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_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameNoLeetCode username. Defaults to LEETCODE_USERNAME.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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. The description adds that this is a composite aggregation touching many metric families (which implies a heavier call than a single-purpose sibling), but it says nothing about cost, caching, staleness, or how the due-review figures relate to get_due_reviews. Nothing contradicts the annotations.

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 sentence with the resource named first and the returned fields enumerated after it. There is no filler and nothing redundant; each listed metric earns its place by telling the agent what will come back.

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-parameter, read-only tool with no output schema, the enumerated field list is genuinely load-bearing because it substitutes for a documented return shape. It falls short only in not describing the form of those values or the scope of 'recent activity' and 'weekly and monthly gains'.

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?

Only one optional parameter exists and the schema documents it at 100% coverage, including the LEETCODE_USERNAME default. The description adds no meaning about the username argument, so the baseline 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?

The description names the resource (progress for a LeetCode user) and enumerates the concrete metrics returned: solved counts by difficulty, ranking, streak, activity, gains, goals and due reviews. It is clear what the tool produces, but it makes no attempt to distinguish itself from siblings such as sync_progress or get_due_reviews, whose territory the field list partly overlaps.

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 guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from the description whether to call this on every turn, only when the user asks about stats, or whether get_due_reviews should be preferred for the review portion of this output.

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