Skip to main content
Glama
Sign In
Interactive LeetCode MCP

Interactive LeetCode MCP

by SPerekrestova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reset_session

Reset the tutoring session for a problem, returning to hint level 0 for a fresh re-attempt.

Instructions

Resets the tutoring session for a problem back to hint level 0. Use when the user wants to re-attempt the problem from scratch.

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": {
      "titleSlug": "<titleSlug>"
    },
    "name": "reset_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleSlugYesThe URL slug of the problem to reset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.4

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description bears full burden. It discloses the reset operation but lacks details on side effects (e.g., loss of progress, code), prerequisites (e.g., is the session active?), and return value. Adequate but not thorough.

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?

Exceptionally concise: one sentence for purpose plus one for usage. No fluff, immediately front-loads the key action. Every word earns its place.

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 simple tool with one required param and no output schema, the description covers purpose and usage. Lacks return behavior or error info, but this is a minor gap given the tool's simplicity.

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% and the description adds minimal context beyond the schema's param description. The description confirms the parameter's role but adds no new constraints or formats.

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

Purpose5/5

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

The description clearly states the tool resets the tutoring session to hint level 0, with a specific verb and resource. It distinguishes its purpose from sibling tools like get_problem_progress or start_problem.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear when-to-use guideline: 'when the user wants to re-attempt the problem from scratch.' However, it does not mention when to avoid using it or explicitly contrast with alternatives.

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

Deploy Server

Other Tools