Skip to main content
Glama

memory_alias

Teach a search-term synonym pair: store term→alias so recall finds content via either, one-way only. Omit both fields to list all aliases. Direction is as taught; teach reverse for symmetric lookup.

Instructions

Teach recall a synonym: pass term + alias to record the pair (both are normalized: lowercased + diacritic-folded). DIRECTION IS ONE-WAY, as taught: querying term also searches alias, NEVER the reverse — a single pair does NOT make the alias side find term-side content. When you want symmetric recall, YOU teach the reverse pair too (configuração→config AND config→configuração; two rows, two calls). memory_retrieve then expands each query term with its recorded aliases (an alias hit grounds and is explained as alias: in matched_terms). recorded is STATE (true = the pair exists after this call — the same replay convention as memory_relate); re-adding an existing pair is an OBSERVABLE no-op: recorded:true + already_recorded:true, keeping the first at — verifiable on the list surface, whose rows carry {term, alias, at}. Pass NEITHER field to list the whole table. Empty/self pairs are typed errors. Aliases are derived, droppable data — never authority. Audited on record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNoThe term recall callers will search with. Pass together with `alias` to record; omit BOTH to list the whole table.
aliasNoThe alias that should also ground `term` (direction is as-taught: term → alias, one-way; the CALLER teaches the reverse pair when it wants symmetric recall).
Behavior5/5

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

With no annotations, the description fully discloses normalization, one-way direction, symmetric recall requirement, listing behavior, re-adding as observable no-op, error conditions, and audited nature. No contradictions.

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

Conciseness4/5

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

Front-loaded with core purpose, then systematically covers normalization, direction, symmetric recall, listing, errors, and audit. All sentences are informative, though slightly verbose; could tighten without losing clarity.

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

Completeness5/5

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

Comprehensive for a tool with no output schema: explains return values (recorded, already_recorded, list rows), all behavioral nuances, and error conditions. No gaps given the complexity.

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 covers 100% of parameters with basic descriptions, but the tool description adds critical semantics: normalization, optionality for listing vs recording, non-empty and non-self requirements, and directionality. Adds significant value beyond schema.

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 the tool teaches a synonym pair (term + alias) with normalization, one-way direction, and symmetric recall requirement. It distinguishes from siblings like memory_retrieve (uses aliases) and memory_relate (relations).

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?

Explicitly explains when to record (pass both fields) and when to list (omit both). Describes the one-way direction and need for reverse pair for symmetric recall. Does not explicitly state when not to use but implies alternatives.

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/menot-you/n-memory'

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