Skip to main content
Glama

memory_list

Retrieve all memory schemas from a specified studio to manage AI agent knowledge structures, with options to paginate results.

Instructions

List all memory schemas defined in the studio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
studioNoStudio name to use. Available: STAGING, MAIN, DEV, PRODUCTION. Default: PRODUCTION
skipNoNumber of memories to skip. Default: 0
takeNoNumber of memories to return. Default: 10

Implementation Reference

  • The execution handler for the 'memory_list' tool. It constructs a GET request to the Pickaxe API endpoint `/studio/memory/list` with optional pagination parameters (skip and take) and returns the JSON response.
    case "memory_list": {
      const skip = args.skip ?? 0;
      const take = args.take ?? 10;
      const result = await pickaxeRequest(`/studio/memory/list?skip=${skip}&take=${take}`, "GET", undefined, studio);
      return JSON.stringify(result, null, 2);
    }
  • src/index.ts:411-428 (registration)
    Registration of the 'memory_list' tool in the tools array. Defines the tool name, description, and input schema (including optional studio, skip, and take parameters). The schema references the shared studioParam helper.
    {
      name: "memory_list",
      description: "List all memory schemas defined in the studio.",
      inputSchema: {
        type: "object",
        properties: {
          studio: studioParam,
          skip: {
            type: "number",
            description: "Number of memories to skip. Default: 0",
          },
          take: {
            type: "number",
            description: "Number of memories to return. Default: 10",
          },
        },
      },
    },
  • Input schema definition for the 'memory_list' tool, specifying the expected parameters and their types/descriptions.
    inputSchema: {
      type: "object",
      properties: {
        studio: studioParam,
        skip: {
          type: "number",
          description: "Number of memories to skip. Default: 0",
        },
        take: {
          type: "number",
          description: "Number of memories to return. Default: 10",
        },
      },
    },
  • Shared helper schema for the 'studio' parameter, used across all tools including memory_list for selecting the Pickaxe studio.
    const studioParam = {
      type: "string",
      description: `Studio name to use. Available: ${configuredStudios.join(", ")}. Default: ${DEFAULT_STUDIO || configuredStudios[0]}`,
    };
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 the action ('List') but fails to describe key behaviors such as pagination mechanics (implied by 'skip' and 'take' parameters), return format, error conditions, or authentication requirements. This leaves significant gaps for a tool with three 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 is front-loaded with the core action and resource, making it easy to parse and understand immediately.

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 list operation with no annotations and no output schema, the description is minimally adequate. It specifies the resource ('memory schemas') and scope ('in the studio'), but lacks details on output structure, pagination behavior, or error handling. Given the tool's moderate complexity (three parameters), it should provide more context to be fully complete.

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?

Schema description coverage is 100%, so the input schema fully documents all three parameters. The description adds no additional parameter semantics beyond what's in the schema, but since the schema is comprehensive, a baseline score of 3 is appropriate as the description doesn't need to compensate.

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 ('List') and resource ('all memory schemas defined in the studio'), making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'memory_get_user' or 'doc_list', but the specificity of 'memory schemas' provides some implicit distinction.

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_get_user' or 'doc_list'. It lacks any mention of prerequisites, exclusions, or contextual triggers for selection, leaving the agent to infer usage based solely on the tool name and description.

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