Skip to main content
Glama
LeetCode Tracker MCP

LeetCode Tracker MCP

by aleprime-gh

analyze_topics

Read-only

Pinpoints under-practiced topics by level and topics with elevated local failure rates, helping users target weak areas and plan focused LeetCode practice.

Instructions

Find the least practiced topics at each level and the topics with the highest local failure rate.

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

Input Schema

NameRequiredDescriptionDefault
limitNoTopics per group. Defaults to 5.
usernameNoLeetCode username. Defaults to LEETCODE_USERNAME.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations supply readOnlyHint=true and openWorldHint=true, so safety and scope are partly covered. The description adds that the tool computes two derived metrics rather than raw data, which is useful behavioral context, but says nothing about data source, freshness, grouping mechanics for 'level', or how results are ordered or returned. With no output schema, the return shape remains unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with zero padding, and the analysis goal is stated before any detail. The only cost is that the compression produces ambiguous phrasing ('each level', 'local failure rate') rather than wasted words.

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 read-only analysis tool with no output schema, the definition should explain what a result item contains and what 'level' and 'local' mean. It establishes the two metrics but leaves the structure and terminology of the returned analysis under-specified, so it is only marginally 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 coverage is 100%; both parameters (limit and username) carry descriptions including defaults and bounds. The description adds no meaning beyond the schema – for example, it never clarifies that 'limit' controls topics per group, matching the two output groups. Baseline 3 applies because the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names two concrete analytical outputs ('least practiced topics' and 'topics with the highest local failure rate'), which is more than a tautology. However, key terms are undefined: 'at each level' never says whether level means difficulty, skill tier, or hierarchy depth, and 'local failure rate' is unexplained jargon. An agent can guess the general purpose but not precisely what the tool computes.

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. It never says whether this should be preferred over get_progress or get_problem_history, nor when running this analysis is appropriate versus another progress tool.

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