Interactive LeetCode MCP

Overview Schema Source Related Servers Discussions Admin

start_problem

Open or resume a tutoring session for a LeetCode problem, necessary to request hints and solutions.

Instructions

Opens (or resumes) a tutoring session for a LeetCode problem. Must be called before request_hint, list_problem_solutions, or get_problem_solution. Idempotent: re-running on a slug the user is already mid-way through preserves their hint progress.

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

Input Schema

Name	Required	Description	Default
`language`	No	Optional: the language the user is solving in. Recorded on the session for future workspace / runner phases.
`titleSlug`	Yes	The URL slug of the problem (e.g., 'two-sum').

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.4Jul 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses idempotency and that re-running preserves hint progress, and mentions that the language parameter is recorded for future phases. However, it does not detail potential side effects, error scenarios, or authentication requirements.

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 sentences that front-load the primary purpose and essential usage constraints. No redundant information; every sentence adds value.

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?

Given two parameters (one required), no output schema, and no annotations, the description adequately covers the tool's purpose, idempotency, and prerequisite role. Could optionally mention return value (e.g., session ID) for completeness, but not necessary.

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 100% with both parameters described. The description adds value beyond schema by explaining that the language parameter is 'recorded on the session for future workspace / runner phases', providing context not in the schema. The titleSlug description is already clear in schema.

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 verb 'Opens (or resumes)' and the resource 'a tutoring session for a LeetCode problem'. It distinguishes itself from siblings by explicitly noting it must be called before several sibling tools (request_hint, list_problem_solutions, get_problem_solution), establishing its role as a session initializer.

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

Usage Guidelines5/5

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

Explicitly states that it must be called before certain siblings (request_hint, list_problem_solutions, get_problem_solution), providing clear usage order. Also indicates idempotency and behavior on re-run, giving context on when to use it and what happens if called multiple times.

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