MemAI

recall

Read-onlyIdempotent

Search saved long-term notes by keyword relevance to retrieve timeless facts, rules, or decisions; returns snippet results with token estimates.

Instructions

Recall long-term knowledge saved with note() (type='note').

The dedicated verb for "bring back what I noted": a BM25 search scoped to type='note', ranked by relevance -- which is what you want for timeless facts/rules/decisions. This (or search(type='note')) is how notes come back by relevance; must_read(type='note') lists the newest.

Returns {"results": [...], "est_tokens": N}. Content is snippet-truncated -- call get_memory(uid) for the full record; a result's est_tokens estimates what that full record costs, and the top-level est_tokens is the sum over the results.

Results carry the same succeeded_by / collapsed annotations search() explains.

Input Schema

Name	Required	Description
`limit`	No	the most results to return.
`query`	Yes	the words to look for; as in search(), more terms find more.
`domain`	No	scopes to a path and everything nested under it, and resolves a bare deep segment the same way search() does.
`offset`	No	where the page starts; `next_offset`, when present, starts the next.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.16.1Oct 16, 2026

addedInput schema / properties / domain / description

Added value: +"scopes to a path and everything nested under it, and resolves a bare deep segment the same way search() does."

removedInput schema / properties / domain / title
```
Removed value: -"Domain"
```
addedInput schema / properties / limit / description
```
Added value: +"the most results to return."
```
removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "where the page starts; `next_offset`, when present, starts the next.",
+  "type": "integer"
+}

addedInput schema / properties / query / description

Added value: +"the words to look for; as in search(), more terms find more."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```
removedInput schema / title
```
Removed value: -"recallArguments"
```

Changed2 schema fields changedv0.1.1Sep 13, 2026

changedInput schema / properties / limit / default
```
Previous value: -20New value: +10
```

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "recallOutput",
-  "type": "object"
-}New value: +null

First observedv0.1.0Jul 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly/idempotent/non-destructive), yet the description adds substantial behavioral context: the return shape, snippet truncation, the need to call get_memory(uid) for full records, and what est_tokens means at both result and top level. This is real disclosure beyond structured data, with only a minor reliance on search() to explain succeeded_by/collapsed.

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

Conciseness4/5

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

Front-loaded with the core purpose and routing, and every paragraph carries information. It is slightly longer than necessary, with some decorative phrasing (the quoted 'bring back what I noted'), which keeps it short of a 5.

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?

Despite having no output schema, the description explains the return payload, the truncation model, and the follow-up call needed for full records. Combined with complete parameter coverage and clear safety annotations, an agent has everything needed to call and interpret this tool.

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 coverage is 100%, so query, limit, offset, and domain are already documented in the schema. The description restates relevance ranking but adds no new parameter-level syntax or format detail, making the baseline 3 appropriate.

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 (recall), resource (long-term notes), and mechanism (BM25 relevance-ranked search scoped to type='note'). It explicitly differentiates itself from search(type='note') and must_read(type='note'), so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance (timeless facts/rules/decisions wanted by relevance) and names the alternatives with their conditions: search(type='note') as the equivalent path and must_read(type='note') for the newest entries. Nothing is left to inference.

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

recall

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools