Skip to main content
Glama
arjshiv

Local Utilities MCP Server

by arjshiv

think

Record and store thoughts for later reference using the Local Utilities MCP Server. This tool helps users capture ideas and maintain a thought log through a simple interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thoughtYesThe thought content to record

Implementation Reference

  • src/mcp/think.ts:67-82 (registration)
    Registers the 'think' MCP tool: defines input schema, handler logic to record thought with timestamp in closure-based state, and returns success response.
    server.tool(
      "think",
      { thought: z.string().min(1, "Thought cannot be empty").describe("The thought content to record") },
      async ({ thought }) => {
        thoughts.push({
          timestamp: new Date().toISOString(),
          content: thought
        });
        return {
          content: [{
            type: "text",
            text: "Thought recorded successfully"
          }]
        };
      }
    );
  • The core handler function for the 'think' tool that appends the user-provided thought to an internal array with a timestamp and responds with a text confirmation.
    async ({ thought }) => {
      thoughts.push({
        timestamp: new Date().toISOString(),
        content: thought
      });
      return {
        content: [{
          type: "text",
          text: "Thought recorded successfully"
        }]
      };
    }
  • Zod schema for 'think' tool input: requires a non-empty string 'thought'.
    { thought: z.string().min(1, "Thought cannot be empty").describe("The thought content to record") },
  • src/index.ts:25-25 (registration)
    Top-level call to register the 'think' tool (and others) on the MCP server instance.
    registerThinkTool(server);
  • Supporting class with methods to manage thoughts (add, retrieve, clear, stats), maintained for testing but registration uses closure state instead.
    export class ThinkToolInternalLogic {
      thoughts: Thought[] = []; // Make public for test access if needed, or add methods
    
      addThought(content: string): void {
        this.thoughts.push({
          timestamp: new Date().toISOString(),
          content
        });
      }
    
      getAllThoughts(): Thought[] {
        return [...this.thoughts];
      }
    
      clearThoughts(): void {
        this.thoughts = [];
      }
    
      getThoughtStats(): ThoughtStats {
        const totalThoughts = this.thoughts.length;
        
        if (totalThoughts === 0) {
          return {
            totalThoughts: 0,
            averageLength: 0,
            oldestThought: null,
            newestThought: null
          };
        }
    
        const averageLength = this.thoughts.reduce((acc, thought) => 
          acc + thought.content.length, 0) / totalThoughts;
    
        return {
          totalThoughts,
          averageLength: parseFloat(averageLength.toFixed(2)), // Keep formatted
          oldestThought: this.thoughts[0].timestamp,
          newestThought: this.thoughts[this.thoughts.length - 1].timestamp
        };
      }
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/arjshiv/localutils-mcp-server'

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