Skip to main content
Glama
jackccrawford

Geniuz

by jackccrawford
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

recall_recent

Retrieve recent memories to see what happened in past sessions. Use at the start of a conversation to recall what the user was working on, decisions made, and relevant context.

Instructions

Get the most recent memories. Use this at the START of every conversation to see what happened in recent sessions. This is how you orient yourself — what was the user working on? What decisions were made? What context matters right now?

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoIf true, returns full content. Default false (gist summaries only).
limitNoNumber of recent memories to return. Default 5.
sinceNoOptional. Only memories from this time on: '24h', '7d', '2w', a date ('2026-09-23'), a local time ('2026-09-23 14:00') or RFC 3339. Use it whenever the question has a time in it ('last week', 'yesterday') — without it, older memories outrank recent ones.
untilNoOptional. Only memories before this time. Same forms as since; a date includes that whole day.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.1
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Optional. Only memories from this time on: '24h', '7d', '2w', a date ('2026-09-23'), a local time ('2026-09-23 14:00') or RFC 3339. Use it whenever the question has a time in it ('last week', 'yesterday') — without it, older memories outrank recent ones.",
+  "type": "string"
+}
    • addedInput schema / properties / until
      Added value: +{
+  "description": "Optional. Only memories before this time. Same forms as since; a date includes that whole day.",
+  "type": "string"
+}
  2. First observedv4.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral insight — default gist summaries vs full content, and the ranking caveat that without 'since' older memories outrank recent ones. But it says nothing about permissions, error behavior, pagination, or the shape of returned records.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are front-loaded and carry the load, but the closing rhetorical triplet ('What was the user working on? What decisions were made? What context matters right now?') is padding that restates the orientation point three times without adding instruction.

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?

For a zero-required-parameter read tool with no output schema and no annotations, the description covers purpose, trigger timing, and output granularity. The remaining gaps — response shape and interplay between limit and since — are minor and partly covered by the schema.

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 all four parameters (full, limit, since, until) are already documented in the schema, including the 'since' ranking caveat. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb+resource ('Get the most recent memories'), which is clear and distinguishable in intent from writing tools like 'remember'. However, it never explicitly differentiates itself from the sibling 'recall' (presumably a broader/query-based retrieval), so the agent must infer the boundary.

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?

Gives a strong, explicit when-to-use rule: 'Use this at the START of every conversation.' That is unusually directive and useful. It stops short of naming rival tools or stating when NOT to use it (e.g., use 'recall' for keyword/topic lookup instead).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools