Skip to main content
Glama
fmangot

Sequential Thinking MVP Server

by fmangot

reset_thinking_session

Clear the current thought sequence and start a new structured reasoning session for step-by-step problem solving

Instructions

Starts a new thinking session, clearing the current thought sequence

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Switch case handling the reset_thinking_session tool: calls resetSession on the thinking manager and returns confirmation with new session ID.
    case 'reset_thinking_session': {
      const newSessionId = thinkingManager.resetSession();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                message: 'New thinking session started',
                sessionId: newSessionId,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Tool schema definition for reset_thinking_session with name, description, and empty input schema (no parameters required).
    export const RESET_SESSION_TOOL: Tool = {
      name: 'reset_thinking_session',
      description: 'Starts a new thinking session, clearing the current thought sequence',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    };
  • Core implementation of session reset in SequentialThinkingManager: generates new secure session ID and initializes empty session.
    public resetSession(): string {
      this.currentSessionId = generateSecureSessionId();
      this.initializeSession(this.currentSessionId);
      return this.currentSessionId;
    }
  • src/index.ts:31-39 (registration)
    MCP server registration: lists tools via ALL_TOOLS (includes reset_thinking_session schema) and dispatches calls to shared handleToolCall function.
    // Handle tool listing
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools: ALL_TOOLS };
    });
    
    // Handle tool calls
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      return handleToolCall(request.params, thinkingManager);
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool clears the current thought sequence, which implies a destructive action, but doesn't specify if this is reversible, what happens to previous data, or any side effects like resetting session state. More context on the mutation's impact is needed.

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?

The description is a single, well-structured sentence that front-loads the key action ('starts a new thinking session') and adds necessary detail ('clearing the current thought sequence') without any wasted words. It's appropriately sized for the tool's simplicity.

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?

Given the tool has no parameters, no output schema, and no annotations, the description covers the basic purpose adequately. However, as a mutation tool (implied by 'clearing'), it lacks details on behavioral traits like reversibility or effects on sibling tools, making it only minimally viable for the context.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, which is efficient, but since there are no parameters to explain, it doesn't fully earn a 5 for adding value beyond the schema.

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 clearly states the action ('starts a new thinking session') and the effect ('clearing the current thought sequence'), which is a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like 'sequential_thinking' which might also involve session management, so it doesn't reach the highest score.

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?

The description implies usage when wanting to start fresh by clearing thoughts, but provides no explicit guidance on when to use this versus alternatives like 'sequential_thinking' or 'get_session_summary', nor any prerequisites or exclusions. It lacks detailed context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fmangot/Mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server