Skip to main content
Glama

recall_recent

Retrieve the most recent memories for a session without providing a search query. Specify the session and optionally the number of memories to return.

Instructions

Get the N most recent memories for a session — no query needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession identifier
limitNoNumber of recent memories to return (default 20)

Implementation Reference

  • src/index.ts:209-220 (registration)
    Tool registration with name 'recall_recent', description, and input schema (sessionId required, limit optional with default 20)
    {
      name: 'recall_recent',
      description: 'Get the N most recent memories for a session — no query needed.',
      inputSchema: {
        type: 'object',
        properties: {
          sessionId:  { type: 'string', description: 'Session identifier' },
          limit:      { type: 'number', description: 'Number of recent memories to return (default 20)', default: 20 },
        },
        required: ['sessionId'],
      },
    },
  • Handler for 'recall_recent' tool: calls memory.recallRecent() with sessionId and limit (default 20), returns JSON results
    case 'recall_recent': {
      const entries = await (memory as any).recallRecent(
        args.sessionId as string,
        (args.limit as number) || 20
      );
      return { content: [{ type: 'text', text: JSON.stringify(entries, null, 2) }] };
    }
  • Compiled JS registration of 'recall_recent' tool with same schema
    {
        name: 'recall_recent',
        description: 'Get the N most recent memories for a session — no query needed.',
        inputSchema: {
            type: 'object',
            properties: {
                sessionId: { type: 'string', description: 'Session identifier' },
                limit: { type: 'number', description: 'Number of recent memories to return (default 20)', default: 20 },
            },
            required: ['sessionId'],
        },
    },
  • Compiled JS handler for 'recall_recent' tool
    case 'recall_recent': {
        const entries = await memory.recallRecent(args.sessionId, args.limit || 20);
        return { content: [{ type: 'text', text: JSON.stringify(entries, null, 2) }] };
    }
Behavior2/5

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

No annotations provided; description only states the basic retrieval without disclosing behavioral traits like idempotency, authentication needs, or error cases.

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?

Single sentence, 10 words, no filler, front-loaded with key information.

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 simple retrieval tool, it is mostly complete but lacks behavioral context; missing details about what constitutes a session and that it is read-only.

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 has 100% coverage, so baseline is 3; description does not add additional semantics beyond the schema definitions.

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 the action (Get) and resource (recent memories) for a session, and distinguishes from siblings like recall and recall_by_time by emphasizing 'no query needed'.

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?

Implies usage for simple retrieval without queries, but does not explicitly compare to siblings or mention when not to use.

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/Cartisien/engram-mcp'

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