Skip to main content
Glama
loaditoutadmin

loaditout-mcp-server

Official

recall_memory

Retrieve saved memories at session start to restore context, installed skills, and user preferences. Filter by type for specific categories.

Instructions

Retrieve previously saved memories from persistent storage. Returns a JSON object with a memories array, each entry containing key, value, and type. Use this at the start of every session to restore context, installed skills, and user preferences. Returns an empty array if no memories exist. Filter by type to retrieve only specific categories of memories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter memories by type. Omit to get all memories.

Implementation Reference

  • Handler function that retrieves saved memories from the API. Accepts an optional 'type' filter, sends a GET request to /memory endpoint, and returns all stored key-value pairs as JSON.
    async function handleRecallMemory(args: {
      type?: string;
    }): Promise<string> {
      const params = new URLSearchParams({ agent_key: AGENT_KEY });
      if (args.type) params.set("type", args.type);
    
      const result = await fetchJSON(`${API_BASE}/memory?${params.toString()}`);
      return JSON.stringify(result, null, 2);
    }
  • Tool definition with name 'recall_memory', description, and input schema defining the optional 'type' parameter with enum values: search, install, preference, context.
    {
      name: "recall_memory",
      description:
        "Retrieve previously saved memories. Returns all stored key-value pairs, optionally filtered by type. Use this at the start of a session to restore context.",
      inputSchema: {
        type: "object" as const,
        properties: {
          type: {
            type: "string",
            enum: ["search", "install", "preference", "context"],
            description: "Filter memories by type. Omit to get all memories.",
          },
        },
      },
    },
  • Tool routing case in the main tool dispatch switch statement that maps the 'recall_memory' name to the handleRecallMemory handler function.
    case "recall_memory":
      resultText = await handleRecallMemory(
        toolArgs as { type?: string }
      );
      break;
Behavior4/5

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

With no annotations, the description fully depends on itself. It discloses the return format (JSON with memories array), empty array if none, and filtering by type. It does not mention any side effects, but as a read-only retrieval, this is adequate. No contradictions with annotations.

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 three sentences long, each providing essential information: purpose, return format, and usage guidance. It is front-loaded and contains no redundant words.

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 single optional parameter and the absence of an output schema, the description adequately explains the return structure (memories array with key, value, type) and the behavior when no memories exist. It is complete for the tool's simplicity.

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?

The only parameter 'type' is fully described in the schema with enum values and a description. The description reiterates the filtering capability but adds no additional meaning beyond the schema. Since schema coverage is 100%, the baseline of 3 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 clearly states the verb 'Retrieve' and the resource 'previously saved memories,' making its purpose unambiguous. It distinguishes itself from sibling tools like 'save_memory' by focusing on retrieval and restoration of context.

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?

The description explicitly advises using this tool at the start of every session to restore context, installed skills, and user preferences, providing clear usage context. However, it does not mention when not to use it or compare it directly with alternative tools.

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/loaditoutadmin/loaditout-mcp-server'

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