Skip to main content
Glama

lore_insert

Insert memories into the store with titles, content, descriptions, scores, and source tags. Create links between memories to define relationships.

Instructions

Insert memories and/or links into the store.

Each memory dict must include:

  • title (str, required): short unique label for the memory

  • content (str, optional): the full text to store

  • description (str, optional): brief summary

  • score (float, optional, default 5.0): initial quality score 0-10

  • source_type (str, optional, default 'observed'): provenance tag. One of: observed, inferred, user_stated, consolidated, injected.

  • links (list[dict[str, Any]], optional): inline links to create after insert. Each link dict: {target_memory_id (str, required), relation_type (str, required), reason? (str)}

Each top-level link dict must include source_memory_id, target_memory_id, relation_type, and reason.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoriesNo
linksNo
forceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so description carries full burden. It states 'Insert' indicating a write operation, but lacks details on side effects, authorization needs, or whether existing memories can be overwritten (force parameter is not explained).

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?

The description is well-structured with bullet points and front-loads the main action. It is moderately long but each part adds value. Could be slightly more concise by removing redundant phrasing.

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?

Provided output schema exists but description does not mention return values. Details for memories and links are thorough, but missing explanation of 'force' parameter. For an insertion tool, this is adequate but not complete.

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 coverage is 0%, but description compensates well for 'memories' and 'links' parameters by specifying required fields and optional fields with defaults. However, it does not mention the 'force' parameter, leaving its role unclear.

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 'Insert memories and/or links into the store.' It details the specific structure of memory dicts and links, distinguishing from sibling tools like lore_search or lore_forget by focusing on insertion.

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 implies use for inserting data, but does not explicitly state when to use this tool versus alternatives like lore_update or lore_reflect. No when-not scenarios or alternative tool mentions.

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/Jessinra/Lorekeeper'

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