Skip to main content
Glama
arjshiv

Local Utilities MCP Server

by arjshiv

get_thoughts

Retrieve all recorded thoughts from the Local Utilities MCP Server to access stored mental notes and ideas.

Instructions

Retrieve all recorded thoughts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp/think.ts:84-97 (registration)
    Registers the get_thoughts MCP tool. The inline handler retrieves a copy of all recorded thoughts from the closure state and returns them as a formatted JSON string in a text content block.
    // Register get_thoughts command
    server.tool(
      "get_thoughts",
      "Retrieve all recorded thoughts",
      async () => {
        const currentThoughts = [...thoughts];
        return {
          content: [{
            type: "text",
            text: JSON.stringify(currentThoughts, null, 2)
          }]
        };
      }
    );
  • TypeScript interface defining the structure of each thought object returned by the get_thoughts tool.
    export interface Thought {
      timestamp: string;
      content: string;
    }
  • src/index.ts:25-25 (registration)
    Invokes the registerThinkTool function on the MCP server, which includes the registration of the get_thoughts tool.
    registerThinkTool(server);
  • Closure state variable that stores the array of recorded thoughts used by the get_thoughts handler.
    let thoughts: Thought[] = [];
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Retrieve all recorded thoughts' implies a read operation but doesn't specify format, pagination, permissions, or what 'all' means (e.g., time range, limit). This is inadequate for a tool with zero annotation coverage.

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 with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool.

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 simple but vague purpose, the description is incomplete. It doesn't explain what 'thoughts' are, how they're returned, or behavioral aspects like rate limits. For a tool with siblings offering related functionality, more 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 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, which is appropriate here. Baseline 4 is correct for zero-parameter tools.

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 ('Retrieve') and resource ('all recorded thoughts'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'get_thought_stats' or 'clear_thoughts', but it's specific enough to understand what it does.

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 provides no guidance on when to use this tool versus alternatives like 'get_thought_stats' or 'clear_thoughts'. There's no mention of context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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