Skip to main content
Glama

memos_recent

List memories from the past few hours to recall recent work. Optionally filter by source tag for targeted retrieval.

Instructions

List recent memories from the last N hours.

Useful for "what was I working on yesterday?". Searches with a wildcard query then sorts client-side by stored_at timestamp.

Args: hours: How many hours back to look (default 24). source: Optional filter on the [source: ...] tag, e.g. "human".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNo
sourceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description reveals internal behavior: 'Searches with a wildcard query then sorts client-side by stored_at timestamp.' With no annotations provided, this is valuable transparency about how the tool works.

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 few sentences long, front-loaded with the purpose, and uses a clean Args section for parameters. Every sentence adds value with no redundancy.

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

Completeness5/5

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

For a simple tool with two optional parameters and an existing output schema, the description covers the purpose, behavior, parameters, and a use case. No additional information seems necessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully explains both parameters: 'hours' (with default and meaning) and 'source' (with example). This adds critical meaning beyond the schema's type/default info.

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?

The description clearly states 'List recent memories from the last N hours' with a specific verb and resource, and provides an example use case. It is immediately distinct from sibling tools 'memos_remember' and 'memos_search'.

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?

It gives a concrete usage scenario ('what was I working on yesterday?'), which helps the agent understand when to invoke it. However, it does not explicitly contrast with sibling tools or state when not to use it.

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/mchosc/memos-mcp-server'

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