Skip to main content
Glama
Sign In
Interactive LeetCode MCP

Interactive LeetCode MCP

by SPerekrestova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_session_state

Retrieve the saved session for a problem to restore context after a restart. Returns null if the problem was not started.

Instructions

Returns the persisted session for a problem, or null if the user has not called start_problem for it. Useful for restoring context after a restart.

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

Input Schema

NameRequiredDescriptionDefault
titleSlugYesThe URL slug of the problem.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.4

TDQS

A4.2/5.0
Behavior4/5

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

Describes return value and null condition; no annotations provided but description is sufficient for a read-only operation.

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, front-loaded with action and use case, no extraneous content.

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?

Adequate for a simple getter with one parameter; could benefit from mentioning return format but overall 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 already fully describes the titleSlug parameter with 100% coverage; description adds no extra meaning.

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?

States clearly that it returns the persisted session for a problem or null, distinguishing from sibling tools like start_problem and reset_session.

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?

Explicitly mentions usefulness for restoring context after restart, but does not provide when-not-to-use or compare to 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