Skip to main content
Glama
arjshiv

Local Utilities MCP Server

by arjshiv

get_thoughts

Retrieve all recorded thoughts from your local storage. Access and review your saved thoughts quickly.

Instructions

Retrieve all recorded thoughts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_thoughts' tool that retrieves all recorded thoughts from the in-memory array and returns them as a JSON string.
    // 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)
          }]
        };
      }
    );
  • src/mcp/think.ts:84-97 (registration)
    The tool is registered on the McpServer using server.tool() with the name 'get_thoughts' and description 'Retrieve all recorded thoughts'.
    // 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)
          }]
        };
      }
    );
Behavior2/5

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

No annotations provided, and description lacks behavioral details such as output format, ordering, or limits. Minimal disclosure beyond the name.

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?

Four-word sentence is maximally concise and front-loaded with the action and object.

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?

For a tool with no parameters, no output schema, and no annotations, the description is minimally adequate but leaves out return format and relationship to siblings like get_thought_stats.

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

Parameters3/5

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

No parameters exist, so description cannot add value beyond schema. Baseline 3 is appropriate as it does not contradict or confuse.

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?

Description clearly states verb 'Retrieve' and resource 'all recorded thoughts', distinguishing from siblings like think (create) and 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 Guidelines2/5

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

No guidance on when to use vs alternatives like get_thought_stats or clear_thoughts. Agent must infer usage from 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