Skip to main content
Glama

brief_memory

Retrieve and summarize scattered memories on a topic into a single structured document, persisted and indexed for future recall.

Instructions

Create a structured memory brief by retrieving and summarizing relevant memories, then persist it as a reusable asset indexed for future recall. Use this when you want to consolidate scattered knowledge on a topic into a single retrievable document. Side effect: writes a new brief asset to disk and indexes it in the vector store for future search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language topic or task to brief, e.g. 'deployment pipeline architecture decisions'
limitNoMaximum number of source memories to include in the brief (default: 8)
scopeNoRestrict search to a specific scope, e.g. 'project:myapp'. Omit to use the default scope
sessionIdNoSession identifier to infer session-scoped search, e.g. 'abc123'
allScopesNoSet to true to search across all scopes instead of the default scope
profileNoRetrieval profile that tunes ranking weights: 'writing' for narrative, 'debug' for technical, 'fact-check' for high-precision
titleNoHuman-readable title for the brief asset, e.g. 'Q1 Auth Migration Summary'. Auto-generated if omitted
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explicitly discloses the side effect: 'writes a new brief asset to disk and indexes it in the vector store for future search.' This is transparent about what the tool does beyond the primary action, though it does not discuss permissions or rate limits.

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?

The description consists of two sentences: the first defines the action and effect, the second gives usage advice and side effects. It is front-loaded with the primary purpose, contains no redundant information, and every sentence serves a clear function.

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?

Given 7 parameters, no output schema, and no annotations, the description covers purpose, usage hint, and side effects. However, it does not describe what the tool returns (e.g., asset ID or summary) nor explain interactions between parameters like scope and allScopes. This leaves gaps for an agent trying to invoke the tool correctly.

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?

The input schema has 100% coverage, with descriptions for all 7 parameters. The tool description does not add additional parameter-specific information beyond what the schema provides. According to guidelines, when coverage is >80%, baseline is 3, and the description does not improve upon that.

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 begins with 'Create a structured memory brief by retrieving and summarizing relevant memories, then persist it as a reusable asset indexed for future recall.' This clearly states the verb (create), resource (memory brief), and outcome (persisted asset). It distinguishes from siblings like search_memory (retrieve only) or store_memory (store raw) by specifying consolidation into a single retrievable document.

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 says 'Use this when you want to consolidate scattered knowledge on a topic into a single retrievable document.' This provides clear context for when to use the tool. However, it does not explicitly state when not to use it or name alternative tools, though the sibling list implies alternatives exist.

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/AliceLJY/recallnest'

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