Skip to main content
Glama

Metis · Memory Curator — Link Memories

link_memories

Create typed relationships between memory entries across different layers to build a lightweight knowledge graph, enabling graph traversal during recall.

Instructions

Create a typed relationship between two memory entries.

Links two entries across any memory layers — episodic, semantic, procedural,
memory (palace), or knowledge. This builds a lightweight knowledge graph on
top of the existing memory layers, enabling graph traversal during recall.

Example relations: 'informed_by', 'contradicts', 'elaborates', 'derived_from',
'supersedes', 'related_to', 'supports', 'led_to'.

Args:
    source_layer: Layer of the source entry ('episodic', 'semantic',
        'procedural', 'memory', 'knowledge').
    source_id: Row ID of the source entry in its layer.
    target_layer: Layer of the target entry.
    target_id: Row ID of the target entry in its layer.
    relation: Relationship type (e.g. 'informed_by', 'contradicts').
    note: Optional free-text note explaining the relationship.

Returns:
    Confirmation of the created link, or an error if it already exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
relationYes
source_idYes
target_idYes
source_layerYes
target_layerYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool creates a link, returns confirmation or error if the link already exists, and builds a knowledge graph. It does not specify permission requirements, existence checks on source/target, or directionality, but these are relatively minor gaps.

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 is well-structured: a concise purpose statement, context about layers and knowledge graph, example relations, then a clean Args list, and finally return value. Every sentence adds value, and it is front-loaded with the core action.

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?

Given the tool's complexity (6 parameters, no annotations, has output schema), the description covers essential aspects: layers, relation types, parameter explanations, return behavior. No further details (e.g., rate limits) are necessary for a simple link creation tool.

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

Parameters5/5

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

The schema has 0% description coverage, but the tool description provides a detailed Args section explaining each parameter (source_layer, source_id, etc.), including example relation types. This fully compensates for the schema's lack of descriptions.

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 'Create a typed relationship between two memory entries,' specifying the verb (Create), resource (typed relationship), and context (memory entries across episodic, semantic, etc., layers). It distinguishes from siblings like 'remember' or 'store_episodic_memory' by focusing on linking rather than storing.

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

Usage Guidelines3/5

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

The description explains the tool's purpose and the layers involved, but does not explicitly state when to use it vs. alternatives or when not to use it. No exclusions or alternative tools are mentioned, leaving the agent to infer usage context.

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/SVerITG/Metis'

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