Skip to main content
Glama

Recall your memories near you (3D memory palace)

recall_nearby_memories
Read-only

Call this BEFORE you decide your next action: it grounds the choice in what you already know about THIS place instead of starting blind. Returns your OWN anchored memories within radiusM of your position (default 20m, max 64m). Or, when you pass regionId, every memory you anchored inside that labeled region (e.g. "my library"). Without query they come back nearest-first. With query (free text describing what you are trying to remember) radius-mode recall is ranked by a hybrid of semantic relevance to the query AND spatial proximity, plus recency, importance, and how recently the place was re-seen, so "what is relevant to what I am doing, near where I stand" is one call. Each entry: {memory_id, kind, event_text, importance, position, distance_m, occurred_at, region}. Only YOUR memories are ever returned, never another agent's. Anchor memories first with append_memory(space, position); pair with build + label_region to construct a navigable memory palace you can revisit and read back. Recall is occlusion-BLIND by default: you remember a memory in the next room even though a wall blocks sight, just as you know what is there without seeing it. Pass lineOfSightOnly:true for a perception-style question instead - restrict results to memories whose subject is currently VISIBLE from where you stand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional free-text description of what you are trying to recall. When given (radius mode), results are ranked by semantic relevance combined with spatial proximity (hybrid recall), not by distance alone.
spaceYes
radiusMNo
regionIdNo
scoringVariantNo
fieldOfViewOnlyNo
lineOfSightOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / regionId / maximum
      Removed value: -9007199254740991
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds significant behavioral context: memories are only yours, not other agents', recall is occlusion-blind by default, lineOutSightOnly changes this, and the hybrid ranking method (semantic + spatial + recency). No contradictions with annotations.

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

Conciseness3/5

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

The description is a single dense paragraph of several sentences. It is front-loaded with the most important instruction ('Call this BEFORE...'), but the block of text could be more concise and structured (e.g., bullet points for modes and options).

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?

Given the tool's complexity (7 parameters, multiple modes, no output schema), the description covers the primary use cases, ranking behavior, occlusion handling, and memory fields returned. It lacks explicit details on the return format and some advanced parameters, but overall provides enough context for an agent to use it correctly.

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 low (14%), but the description compensates by explaining the key parameters: space (implied), radiusM (default 20m, max 64m), regionId, query, and lineOfSightOnly. However, it omits fieldOfViewOnly and scoringVariant, leaving some parameters undocumented in both schema and description.

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 starts by stating exactly when to use this tool: 'Call this BEFORE you decide your next action.' It clearly identifies the verb 'recall' and resource 'memories near you', and distinguishes itself from sibling tools like append_memory and search_memories by focusing on spatial recall.

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?

The description provides explicit guidance on when to call the tool ('before you decide your next action') and explains the two modes (radius vs regionId, with/without query). It also mentions prerequisites (anchor first with append_memory) and pairing with build and label_region, but does not explicitly state when not to use it or alternative tools for non-spatial recall.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources