Skip to main content
Glama

memory_get_user

Retrieve user memories from the Pickaxe platform by email, with options to filter by memory type, skip records, and limit results for efficient data access.

Instructions

Get all collected memories for a specific user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
studioNoStudio name to use. Available: STAGING, MAIN, DEV, PRODUCTION. Default: PRODUCTION
emailYesThe user's email address
memoryIdNoOptional: specific memory schema ID to filter by
skipNoNumber of memories to skip. Default: 0
takeNoNumber of memories to return. Default: 10

Implementation Reference

  • Switch case that handles execution of the 'memory_get_user' tool by building a query URL with email, optional memoryId, skip, and take parameters, then performing a GET request via pickaxeRequest and returning the JSON-stringified result.
    case "memory_get_user": {
      let url = `/studio/memory/user/${encodeURIComponent(args.email as string)}?`;
      if (args.memoryId) url += `memoryId=${args.memoryId}&`;
      url += `skip=${args.skip ?? 0}&take=${args.take ?? 10}`;
      const result = await pickaxeRequest(url, "GET", undefined, studio);
      return JSON.stringify(result, null, 2);
    }
  • The input schema definition for the 'memory_get_user' tool within the tools array, specifying properties for studio, email (required), memoryId, skip, and take.
    {
      name: "memory_get_user",
      description: "Get all collected memories for a specific user.",
      inputSchema: {
        type: "object",
        properties: {
          studio: studioParam,
          email: {
            type: "string",
            description: "The user's email address",
          },
          memoryId: {
            type: "string",
            description: "Optional: specific memory schema ID to filter by",
          },
          skip: {
            type: "number",
            description: "Number of memories to skip. Default: 0",
          },
          take: {
            type: "number",
            description: "Number of memories to return. Default: 10",
          },
        },
        required: ["email"],
      },
    },
  • src/index.ts:616-618 (registration)
    Registration of the tool list handler that returns the 'tools' array containing the 'memory_get_user' schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a 'Get' operation, implying read-only behavior, but doesn't mention permissions, rate limits, pagination details (beyond implied by skip/take), or what 'collected memories' entails. This leaves significant gaps for a tool with 5 parameters.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for its function, making it easy to parse quickly.

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 the complexity (5 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain what 'memories' are, the return format, error conditions, or behavioral nuances like pagination limits. For a data retrieval tool with multiple parameters, more context is needed to guide effective use.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no additional semantic context beyond implying filtering by user and memoryId, which is already covered in the schema. This meets the baseline for high schema coverage.

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 verb ('Get') and resource ('collected memories for a specific user'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'memory_list' or 'user_get', which might have overlapping functionality, so it doesn't reach the highest score of 5.

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 'memory_list' or 'user_get'. It lacks context about prerequisites, exclusions, or specific scenarios, leaving the agent with minimal usage direction.

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/aplaceforallmystuff/mcp-pickaxe'

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