Skip to main content
Glama
LeetCode Tracker MCP

LeetCode Tracker MCP

by aleprime-gh

set_goal

Set a target for total solved LeetCode problems in a category, optionally by deadline; set the target to 0 to remove that goal.

Instructions

Set a target for the total number of solved problems in a category. A target of 0 removes that goal.

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": {
      "metric": "<metric>",
      "target": "<target>"
    },
    "name": "set_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricYes
targetYesTotal solved count to reach, not an increment.
deadlineNoOptional date in YYYY-MM-DD format.

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?

With no annotations supplied, the description carries the full behavioral burden and does disclose one important trait: a target of 0 removes the goal, which is effectively a deletion path the agent must know about. It does not say whether setting a target overwrites an existing one, what happens to a previously set deadline, whether any permissions are required, 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 short sentences, front-loaded with the action and followed by the one non-obvious edge case. Nothing is redundant or padded.

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 mutation tool with no annotations and no output schema, the description covers the core action and the zero-target deletion case but omits overwrite semantics, deadline behavior over time, and any indication of the result. It is adequate to attempt a call but not complete for a write operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is a moderate 67%, and the description compensates by clarifying that the metric selects a category scope and that a target of 0 is a removal sentinel rather than a value. The deadline parameter is left to the schema, which documents it as an optional YYYY-MM-DD date, so the remaining gap is minor.

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 a specific verb and resource ('Set a target for the total number of solved problems in a category') and scopes it to a per-category target, which is clearly distinct from read-oriented siblings like get_progress or get_due_reviews. It stops short of naming a sibling alternative, but the goal-setting action is unambiguous.

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 explicit when-to-use or when-not-to-use guidance, and no reference to any alternative tool for viewing or adjusting progress. The use case is only inferable from the verb 'Set a target', leaving the agent to guess whether this is the right tool for inspecting versus defining goals.

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