Skip to main content
Glama
LeetCode Tracker MCP

LeetCode Tracker MCP

by aleprime-gh

log_attempt

Record a LeetCode practice attempt with time, confidence, and notes, then schedule the next spaced-repetition review.

Instructions

Record a practice attempt with time, confidence and notes, then schedule the next spaced-repetition review.

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>",
      "accepted": "<accepted>"
    },
    "name": "log_attempt"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoApproach, mistakes or insights.
minutesNoTime spent in minutes.
problemYesProblem slug or URL, for example two-sum.
acceptedYesWhether the attempt ended with a working solution.
confidenceNo1 = could not solve it, 3 = solved with effort, 5 = solved easily.

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?

With no annotations, the description carries the full behavioral burden and usefully discloses that the tool schedules the next spaced-repetition review. It does not explain idempotency, duplicate-attempt behavior, permission requirements, or what the scheduling depends on, leaving meaningful gaps for a mutation tool.

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?

The description is a single front-loaded sentence with no wasted wording. It efficiently combines the primary action with the most important side effect.

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 moderate-complexity logging tool with no annotations and no output schema, the description conveys the core action and the automatic scheduling side effect. It leaves some behavioral detail unstated, but the fully documented schema covers the parameters, so the definition is largely complete.

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 the input schema already documents all five parameters in detail. The description adds no parameter-level semantics beyond listing time, confidence, and notes, and omits problem and accepted entirely, so the baseline of 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 states a specific verb and resource: 'Record a practice attempt' with time, confidence, and notes. It also mentions the automatic scheduling side effect, giving an agent a clear sense of the tool's purpose, though it does not explicitly distinguish itself from retrieval siblings like get_problem_history.

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 'Record a practice attempt', suggesting it is called after completing a problem. However, there is no explicit when-to-use guidance, no exclusions, and no reference to alternatives such as get_due_reviews or get_problem_history.

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