Skip to main content
Glama

get_thinking_summary

Retrieve a complete summary of the current thinking session, including all analysis steps and reasoning paths.

Instructions

Get a complete summary of the current thinking session with all steps and analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get_thinking_summary' tool. It checks if there are thinking steps, generates a formatted summary of all steps including status, timestamps, reasoning, and categories, and returns it as text content. Handles empty session and errors.
      async () => {
        try {
          if (thinkingSession.currentSteps.length === 0) {
            return {
              content: [{
                type: "text",
                text: "📝 **No Active Thinking Session**\n\nUse 'sequential_thinking' to start your first thought."
              }]
            };
          }
          
          const targetSteps = thinkingSession.metadata?.target_steps;
          const progress = targetSteps ? ` (${thinkingSession.currentSteps.length}/${targetSteps})` : '';
          
          let content = `📋 **Thinking Session Summary${progress}**\n\n`;
          content += `**Status**: ${thinkingSession.isComplete ? 'Complete ✅' : 'In Progress 🔄'}\n`;
          content += `**Total Steps**: ${thinkingSession.currentSteps.length}\n`;
          content += `**Started**: ${thinkingSession.currentSteps[0]?.timestamp ? new Date(thinkingSession.currentSteps[0].timestamp).toLocaleString() : 'Unknown'}\n\n`;
          
          content += "**Complete Thinking Chain:**\n";
          thinkingSession.currentSteps.forEach((step, index) => {
            const categoryLabel = step.category ? ` [${step.category}]` : '';
            content += `**${step.id}.${categoryLabel}** ${step.thought}\n`;
            if (step.reasoning) {
              content += `   *Reasoning: ${step.reasoning}*\n`;
            }
            content += '\n';
          });
          
          if (thinkingSession.summary) {
            content += `**Session Summary**: ${thinkingSession.summary}\n`;
          }
          
          if (thinkingSession.pdfContext) {
            content += `**PDF Context**: ${thinkingSession.pdfContext.filename || 'Document loaded'}\n`;
          }
          
          return {
            content: [{
              type: "text", 
              text: content
            }]
          };
          
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `❌ **Error getting thinking summary**: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    );
  • MCP tool registration using server.tool(). Registers 'get_thinking_summary' with empty input schema {} and inline async handler function. No parameters required.
    server.tool(
      "get_thinking_summary",
      "Get a complete summary of the current thinking session with all steps and analysis",
      {},
      async () => {
        try {
          if (thinkingSession.currentSteps.length === 0) {
            return {
              content: [{
                type: "text",
                text: "📝 **No Active Thinking Session**\n\nUse 'sequential_thinking' to start your first thought."
              }]
            };
          }
          
          const targetSteps = thinkingSession.metadata?.target_steps;
          const progress = targetSteps ? ` (${thinkingSession.currentSteps.length}/${targetSteps})` : '';
          
          let content = `📋 **Thinking Session Summary${progress}**\n\n`;
          content += `**Status**: ${thinkingSession.isComplete ? 'Complete ✅' : 'In Progress 🔄'}\n`;
          content += `**Total Steps**: ${thinkingSession.currentSteps.length}\n`;
          content += `**Started**: ${thinkingSession.currentSteps[0]?.timestamp ? new Date(thinkingSession.currentSteps[0].timestamp).toLocaleString() : 'Unknown'}\n\n`;
          
          content += "**Complete Thinking Chain:**\n";
          thinkingSession.currentSteps.forEach((step, index) => {
            const categoryLabel = step.category ? ` [${step.category}]` : '';
            content += `**${step.id}.${categoryLabel}** ${step.thought}\n`;
            if (step.reasoning) {
              content += `   *Reasoning: ${step.reasoning}*\n`;
            }
            content += '\n';
          });
          
          if (thinkingSession.summary) {
            content += `**Session Summary**: ${thinkingSession.summary}\n`;
          }
          
          if (thinkingSession.pdfContext) {
            content += `**PDF Context**: ${thinkingSession.pdfContext.filename || 'Document loaded'}\n`;
          }
          
          return {
            content: [{
              type: "text", 
              text: content
            }]
          };
          
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `❌ **Error getting thinking summary**: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    );
  • Empty Zod schema indicating the tool takes no input parameters.
    {},
  • Global thinkingSession state object used by the tool to store and retrieve the list of thinking steps for summarization.
    let thinkingSession: ThinkingSession = {
      currentSteps: [],
      totalSteps: 0,
      isComplete: false
    };
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 retrieves a summary but doesn't clarify if this is a read-only operation, whether it affects the session state, what format the output takes, or any limitations (e.g., session must be active). This leaves significant gaps for a tool that likely interacts with session data.

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, efficient sentence that front-loads the core purpose ('Get a complete summary') and adds necessary detail ('with all steps and analysis'). There is no wasted wording, making it highly concise and well-structured.

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 and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what a 'thinking session' entails, the format of the summary, or how it integrates with sibling tools. For a tool in a complex environment with many siblings, more context would be helpful.

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 doesn't add parameter details, which is appropriate here. Baseline is 4 for zero parameters, as it avoids unnecessary complexity.

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 verb ('Get') and resource ('complete summary of the current thinking session'), specifying it includes 'all steps and analysis'. However, it doesn't differentiate from siblings like 'reset_thinking' or 'sequential_thinking', which are related but distinct operations.

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 for retrieving a summary of a thinking session, but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'reset_thinking' to clear the session or 'sequential_thinking' for step-by-step processing). No prerequisites or exclusions are mentioned.

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/multiluca2020/visum-thinker-mcp-server'

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