Skip to main content
Glama

recall

Semantically search long-term memory for insights, digests, and observations. Returns relevant snippet previews based on meaning, not exact keywords.

Instructions

Semantic recall from long-term memory (demo.marsvault_chunks) using Jina embeddings. Returns preview snippets (~80 chars) per match by default — use get_summary for a longer excerpt or get_full for complete chunk text. Searches promoted insights, digests, and archived knowledge using vector similarity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoWhich persona profile to search in (e.g. "coco", "toto", "system")demo
typeNoFilter by chunk type (e.g. "insight", "digest", "observation")
limitNoMaximum number of chunks to return (default 5)
queryYesNatural language query describing what knowledge you need. The system finds semantically similar chunks — describe the concept, not just keywords.
scopeNoSearch scope: "this_body" for current profile only, "all_bodies" for cross-persona searchthis_body
agent_bodyNoFilter to a specific persona/body scope
environmentNoFilter to a specific environment label
debug_explainNoWhen true, include token overlap details in each result for debugging relevance
include_globalNoInclude globally visible chunks in results
include_sharedNoInclude shared-visibility chunks in results
min_similarityNoMinimum cosine similarity threshold. Raise for higher precision, lower for broader recall.
include_privateNoInclude private chunks in results
Behavior3/5

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

No annotations are provided, so the description carries full burden. It implies a read-only search operation but does not explicitly state it is non-destructive, authorization requirements, or rate limits. The description is adequate but could be more explicit about safety.

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 with zero waste, front-loaded with key information, and clearly structured.

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 12 parameters and no output schema, the description explains the output format and sibling tools but does not elaborate on filtering parameters like scope or body beyond the schema.

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 description coverage is 100%, so baseline is 3. The description does not add meaningful details to individual parameters beyond what the schema provides.

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 clearly states it performs semantic recall from long-term memory using embeddings, returns preview snippets, and explicitly distinguishes itself from sibling tools get_summary and get_full.

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?

Provides explicit guidance on when to use this tool versus alternatives: 'use get_summary for a longer excerpt or get_full for complete chunk text.'

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/Marsmanleo/MarsNMe'

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