Skip to main content
Glama
cgize

MCP Think Tool Server

get_thoughts

Retrieve all recorded thoughts from the current session to review and refine your reasoning process, enhancing structured problem-solving and decision-making clarity.

Instructions

Retrieve all thoughts recorded in the current session to review your reasoning process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for 'get_thoughts' tool: checks if thoughtsLog is empty, if so returns a message; otherwise formats all thoughts with timestamps and indices into a text response.
    async () => {
      if (this.thoughtsLog.length === 0) {
        return {
          content: [{ type: "text", text: "No thoughts have been recorded yet." }]
        };
      }
      
      const formattedThoughts = this.thoughtsLog.map((entry, index) => 
        `Thought #${index + 1} (${entry.timestamp}):\n${entry.thought}\n`
      );
      
      return {
        content: [{ type: "text", text: formattedThoughts.join("\n") }]
      };
    }
  • src/index.ts:54-73 (registration)
    Registration of the 'get_thoughts' tool via this.server.tool(), including name, description (no input schema), and inline handler function.
    // Register the get_thoughts tool
    this.server.tool(
      "get_thoughts",
      "Retrieve all thoughts recorded in the current session to review your reasoning process.",
      async () => {
        if (this.thoughtsLog.length === 0) {
          return {
            content: [{ type: "text", text: "No thoughts have been recorded yet." }]
          };
        }
        
        const formattedThoughts = this.thoughtsLog.map((entry, index) => 
          `Thought #${index + 1} (${entry.timestamp}):\n${entry.thought}\n`
        );
        
        return {
          content: [{ type: "text", text: formattedThoughts.join("\n") }]
        };
      }
    );
  • Interface defining the structure of each thought record stored in thoughtsLog, used by the get_thoughts handler.
    interface ThoughtRecord {
      timestamp: string;
      thought: string;
    }
  • Private array storing all ThoughtRecord entries, which the get_thoughts handler reads from.
    private thoughtsLog: ThoughtRecord[] = [];
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves all thoughts, but doesn't disclose behavioral traits such as whether it returns a list or single object, pagination, rate limits, or error conditions. The description is minimal and lacks operational details.

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 purpose ('Retrieve all thoughts...') and adds context ('to review your reasoning process') without waste. Every word contributes to understanding the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a read operation with potential complexity (retrieving 'all thoughts'), the description is incomplete. It doesn't explain return values, format, or any behavioral aspects like ordering or limits, leaving gaps for an AI agent to use the tool effectively.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could have mentioned if any implicit parameters (like session context) are involved. Baseline is 4 for zero parameters.

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 'retrieve' and resource 'thoughts recorded in the current session' with the purpose 'to review your reasoning process.' It distinguishes from siblings like 'clear_thoughts' (deletion) and 'think' (creation) by focusing on retrieval, though it doesn't explicitly contrast with 'get_thought_stats' (statistics).

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

Usage Guidelines3/5

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

The description implies usage context ('current session,' 'review reasoning process') but doesn't explicitly state when to use this tool versus alternatives like 'get_thought_stats' for statistics or 'think' for creating thoughts. No exclusions or prerequisites 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

Related 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/cgize/claude-mcp-think-tool'

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