Skip to main content
Glama
arjshiv

Local Utilities MCP Server

by arjshiv

clear_thoughts

Remove all stored thoughts from the system. Use this to reset your recorded notes.

Instructions

Clear all recorded thoughts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The clearThoughts() method on the ThinkToolInternalLogic class that resets the thoughts array.
    clearThoughts(): void {
      this.thoughts = [];
    }
  • The 'clear_thoughts' MCP tool registration with its async handler that clears all recorded thoughts and returns a count.
    // Register clear_thoughts command
    server.tool(
      "clear_thoughts",
      "Clear all recorded thoughts",
      async () => {
        const count = thoughts.length;
        thoughts = []; // Reset the array
        return {
          content: [{
            type: "text",
            text: `Cleared ${count} recorded thoughts.`
          }]
        };
      }
    );
  • Registration of the 'clear_thoughts' tool on the MCP server using server.tool().
    // Register clear_thoughts command
    server.tool(
      "clear_thoughts",
      "Clear all recorded thoughts",
      async () => {
        const count = thoughts.length;
        thoughts = []; // Reset the array
        return {
          content: [{
            type: "text",
            text: `Cleared ${count} recorded thoughts.`
          }]
        };
      }
    );
  • Compiled handler for 'clear_thoughts' MCP tool that clears thoughts and returns count.
    // Register clear_thoughts command
    server.tool("clear_thoughts", "Clear all recorded thoughts", async () => {
        const count = thoughts.length;
        thoughts = []; // Reset the array
        return {
            content: [{
                    type: "text",
                    text: `Cleared ${count} recorded thoughts.`
                }]
        };
    });
Behavior3/5

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

The description implies a destructive action (clearing all thoughts) but does not disclose behavioral traits like permanence, undo capability, or confirmation requirements. Since no annotations are provided, the description carries the full burden, which is only partially met.

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 sentence with no extraneous information, efficiently conveying the tool's purpose.

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

Completeness5/5

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

Given the tool's simplicity (no parameters, no output schema), the description fully specifies what the tool does. No additional context is needed.

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 no parameters, so the input schema coverage is 100%. The description adds no parameter information, but with zero parameters, a baseline of 4 is appropriate.

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?

The description 'Clear all recorded thoughts' uses a specific verb ('clear') and resource ('recorded thoughts'), clearly distinguishing it from sibling tools like 'get_thoughts' (retrieval) and 'think' (creation).

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?

While the purpose is clear, the description provides no guidance on when to use this tool versus alternatives (e.g., using 'get_thoughts' first) or warnings about irreversible action. However, for a simple deletion tool, the lack of detailed guidelines is less critical.

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