Skip to main content
Glama

remember

Store information for later recall to persist data across AI agent sessions, enabling memory retention and organized storage with optional categorization.

Instructions

Store a memory for later recall. Use this to persist information across sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe information to remember
namespaceNoOptional namespace/category (default: "default")
metadataNoOptional metadata tags

Implementation Reference

  • src/index.js:31-43 (registration)
    Registration of the 'remember' tool in the ListToolsRequestSchema handler.
    {
      name: 'remember',
      description: 'Store a memory for later recall. Use this to persist information across sessions.',
      inputSchema: {
        type: 'object',
        properties: {
          content: { type: 'string', description: 'The information to remember' },
          namespace: { type: 'string', description: 'Optional namespace/category (default: "default")' },
          metadata: { type: 'object', description: 'Optional metadata tags' },
        },
        required: ['content'],
      },
    },
  • Handler implementation for the 'remember' tool within the CallToolRequestSchema handler.
    case 'remember':
      result = await call('POST', '/memories', args);
      return { content: [{ type: 'text', text: `Memory stored with ID: ${result.id}` }] };
Behavior3/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 correctly indicates the persistent nature ('across sessions') and mutation ('Store'), but lacks details on return values, idempotency, overwrite behavior, or error conditions that would help an agent predict outcomes.

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 consists of two tightly constructed sentences with zero redundancy. It is front-loaded with the action verb and immediately follows with the value proposition ('across sessions'), making it an exemplar of efficient technical writing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (3 parameters with full schema coverage) and lack of output schema, the description adequately covers the essential function. It could be improved by mentioning the return type or success confirmation, but it provides sufficient context for an agent to invoke the tool correctly.

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 input schema has 100% description coverage, providing a baseline of 3. The description mentions 'Store a memory' which loosely maps to the 'content' parameter, but adds no specific semantic guidance, examples, or format constraints beyond what the schema already provides.

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 ('Store a memory') and the resource, distinguishing it implicitly from sibling 'recall' by specifying this is for storage 'for later recall'. It effectively communicates the tool's directionality (write vs read).

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 phrase 'Use this to persist information across sessions' provides explicit guidance on when to use the tool (for cross-session persistence). While it doesn't explicitly name alternatives like 'recall' or warn against misuse, it establishes a clear usage context.

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/andrewpetecoleman-cloud/agentmemo-mcp'

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