Skip to main content
Glama
LeetCode Tracker MCP

LeetCode Tracker MCP

by aleprime-gh

sync_progress

Import accepted LeetCode submissions and record today's progress snapshot; run it regularly so accepted work is not missed when a LeetCode session is unavailable and only 20 submissions are exposed.

Instructions

Import accepted submissions from LeetCode and record today's progress snapshot. Without a session LeetCode exposes only the latest 20 accepted submissions, so sync regularly.

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": "sync_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameNoLeetCode username. Defaults to LEETCODE_USERNAME.
full_historyNoImport all submissions, including failed ones. Requires LEETCODE_SESSION.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the tool writes data (imports submissions, records a snapshot) and that LeetCode caps results at the 20 most recent accepted submissions without a session. It does not say whether repeat syncs duplicate or upsert records, what authentication is needed by default, or what the call returns.

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?

Two tight sentences, zero redundancy. The core action is front-loaded and the operational caveat plus 'sync regularly' takeaway follow immediately, each earning its place.

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 two-parameter mutation tool with no annotations and no output schema, the description covers purpose, the key external limit, and syncing cadence. It leaves open what a sync actually returns and how repeated runs interact with previously imported data, which matters for a write tool.

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 parameters are already documented, including the LEETCODE_USERNAME default and the LEETCODE_SESSION requirement on full_history. The description reinforces the session constraint by explaining the 20-submission limit, but adds no new syntax or format detail beyond the schema. 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 uses a specific verb-and-resource pairing: 'Import accepted submissions from LeetCode and record today's progress snapshot.' That clearly separates it from read-oriented siblings such as get_progress or get_problem_history, which retrieve rather than import. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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 rather than stated: the note that only the latest 20 accepted submissions are exposed 'without a session' suggests syncing often, and 'sync regularly' gives a cadence. There is no explicit when-to-use versus when-not guidance and no named alternative for cases like backfilling history or reading existing progress.

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