Skip to main content
Glama

memory_recall

Recall relevant memories by querying with filters like mood, tags, date, and type, boosting results by matching emotional state or context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moodNoCurrent mood - boosts recall of memories encoded in similar emotional state
tagsNoOnly return episodic memories with these tags
afterNoOnly return memories created after this ISO date
limitNoMax results (default 10)
queryYesSearch query to match against memories
scopeNoagent restricts recall to this MCP server agent identity. shared searches the whole store. Defaults to shared for backward compatibility.
typesNoMemory types to search
beforeNoOnly return memories created before this ISO date
contextNoRetrieval context - memories encoded in matching context get boosted
sourcesNoOnly return episodic memories from these sources
retrievalNoRetrieval strategy. hybrid is the default (vector + FTS/BM25 fusion); vector bypasses FTS for lower latency but loses lexical exact-match signal.
min_confidenceNoMinimum confidence threshold

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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