Skip to main content
Glama

mimir_recall

Read-only

Search stored facts, decisions, and architecture notes using keyword search. Results sorted by relevance with expanded summaries returned.

Instructions

Search entities with FTS5 keyword search. Words are OR'd together. Returns entities sorted by relevance with expanded content/summary fields at top level. Use this to find previously stored facts, decisions, or architecture notes. When encryption is enabled, body_json is decrypted transparently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoSearch mode: 'fts5' (keyword), 'dense' (vector), or 'hybrid' (fused via RRF)fts5
typeNoFilter by entity type, e.g. 'insight' or 'reference'
limitNoMaximum number of results to return (max 1000)
queryYesSearch query — words are OR'd together for broad recall
offsetNoNumber of results to skip for pagination
agent_idNoAgent identity filter (v1.2.0). When set, only entities with a matching agent_id are returned. Omit for no agent filtering.
categoryNoFilter by category, e.g. 'decision' or 'architecture'
expansionNoConfiguration for FTS5 query expansion using Porter stemming
min_decayNoMinimum decay score threshold 0.0–1.0 — higher values return fresher results
topic_pathNoFilter by topic path prefix, e.g. 'architecture/'
preview_capNoIf set, truncate body_json at N chars and append drill-down footer. Use mimir_get_entity to read full body.
trust_weightNoAdditive boost for provenance/trust (default 0.15, on by default) — verified sources rank above unverified AI drafts on the same topic. Verified entities get the full boost; unverified ones are scaled by certainty. Set 0 to disable. Never penalizes.
content_weightNoAdditive boost for content witness — rewards entities whose body text literally contains query terms. Damped by body length. Never penalizes.
workspace_hashNoWorkspace scope filter (v1.2.0). When set, only entities with a matching workspace_hash are returned. Omit for no workspace filtering.
include_archivedNoInclude archived (soft-deleted) entities in results
diversity_halvingNoPer-keyword diversity quota factor (1.0=disabled). Each distinct matched keyword gets ceil(N x halving^n) slots — first keyword N, second N/2, etc.
recency_half_life_secsNoTime-aware ranking for mode='hybrid' (default off). When set, each fused result's score is multiplied by 0.5^(age / this), where age is seconds since the memory was created — so a memory this many seconds old keeps half its weight and recent context outranks older but similar hits. Omit for relevance-only ranking.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoMatching entities with expanded body_json fields at top level
totalNoNumber of results returned
variantsNoNumber of query variants used when expansion is enabled
Behavior4/5

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

Annotations already declare readOnlyHint=true; description adds valuable behavioral details: OR'ing of words, relevance sorting, expanded fields, and transparent decryption of body_json, which is beyond what annotations offer.

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?

Three sentences, front-loaded with key information, no fluff. Every sentence adds value.

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?

Despite a complex tool with 17 parameters and output schema, the description omits mention of search modes (fts5, dense, hybrid) and filtering capabilities, leaving gaps for a complete understanding.

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% with each parameter already described; the tool description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

Clearly states it searches entities with FTS5 keyword search, but does not explicitly differentiate from sibling tools that may offer alternative search methods like vector or hybrid.

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?

Provides use cases (find facts, decisions, architecture notes) but lacks explicit guidance on when not to use or when alternatives like mimir_recall_when might be better.

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/Perseus-Computing-LLC/perseus-vault'

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