PseudoLife-MCP

Official

Overview Schema Source Related Servers Discussions Admin

memory_recent

Read-only

List the N most recently stored memories, newest first, to catch up at the start of a session or see what was just stored. Filter by tags, sources, or episodes.

Instructions

List the N most recently stored memories, newest first — timestamp order, not relevance. Useful for "what did I just store?" and for catching up at the start of a session. The sources/episodes/ tags filters AND-combine.

Input Schema

Name	Required	Description
`n`	No	How many entries to return; positive integer.
`tags`	No	Keep only entries carrying one of these tags.
`sources`	No	Keep only entries with one of these source tags.
`verbose`	No	Full per-entry metadata; default entries are compact.
`episodes`	No	Keep only entries stamped with one of these episode ids.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.18.1Oct 14, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- changedInput schema / properties / n / description
```
Previous value: -"How many entries to return."New value: +"How many entries to return; positive integer."
```
- addedInput schema / properties / n / minimum
```
Added value: +1
```

Changed5 schema fields changedv0.15.0Sep 3, 2026

addedInput schema / properties / episodes / description

Added value: +"Keep only entries stamped with one of these episode ids."

addedInput schema / properties / n / description
```
Added value: +"How many entries to return."
```

addedInput schema / properties / sources / description

Added value: +"Keep only entries with one of these source tags."

addedInput schema / properties / tags / description

Added value: +"Keep only entries carrying one of these tags."

addedInput schema / properties / verbose / description

Added value: +"Full per-entry metadata; default entries are compact."

First observedv0.11.0Jul 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, explaining the safety profile, so the description adds the ordering semantics (timestamp vs relevance) and the filter combination rule ('AND-combine'). It does not discuss result bounding/pagination beyond the n limit, so it is solid but not exhaustive.

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?

Two sentences, zero filler, with the ordering constraint front-loaded before the use cases. Every clause earns its place.

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?

An output schema exists so return shape needn't be explained; the description covers purpose, ordering, and filter interaction. It could be marginally more complete by naming the relevance-based sibling it contrasts with, but nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the schema: the sources/episodes/tags filters AND-combine (the schema does not state the combination operator). That is genuine added value over the per-parameter descriptions.

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?

States a specific verb (List) and resource (most recently stored memories) plus the ordering contract ('newest first — timestamp order, not relevance'), which implicitly separates it from the relevance-ranked memory_search sibling. An agent can select it without opening either schema.

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 concrete when-to-use contexts: 'what did I just store?' and catching up at session start. It stops short of naming the alternative tool (memory_search/memory_recall) for contrast, so the routing is contextual rather than explicit.

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