Skip to main content
Glama
Marsmanleo

marsnme

by Marsmanleo
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

insert_memory

Store short-term memories that auto-expire after 7 days. Capture session notes, decisions, and observations for temporary context.

Instructions

Store a short-term demo memory into demo.memories (ephemeral context that auto-expires). Use this to capture observations, decisions, session notes, or any context worth remembering temporarily. Memories last 7 days by default unless expires_at is set. For permanent knowledge, use memory_ingest instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesThe memory content to store. Be specific and include relevant context — this text is used for semantic search later.
tagsNoCategorization labels for filtering (e.g. ["decision", "architecture", "bugfix"])
sourceYes
agent_bodyNoWhich persona/agent body this memory belongs to (e.g. "coco", "toto"). Defaults to the profile of this server.
expires_atNoCustom expiration time in ISO 8601 format (e.g. "2026-06-17T00:00:00Z"). Defaults to 7 days from now if omitted.
session_idYesUnique identifier for the current session/conversation. Used to group related memories together.
environmentNoDeployment environment label (e.g. "production", "staging"). Defaults to MCP_ENVIRONMENT if set.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "perplexity",
-  "cursor",
-  "warp",
-  "openclaw",
-  "hermes"
-]New value: +[
+  "perplexity",
+  "cursor",
+  "warp",
+  "openclaw",
+  "hermes",
+  "draft",
+  "grok"
+]
  2. Changed6 schema fields changedv0.1.1
    • changedInput schema / properties / agent_body / description
      Previous value: -"Optional body label (default inferred from source)"New value: +"Which persona/agent body this memory belongs to (e.g. \"coco\", \"toto\"). Defaults to the profile of this server."
    • changedInput schema / properties / body / description
      Previous value: -"Memory content text"New value: +"The memory content to store. Be specific and include relevant context — this text is used for semantic search later."
    • changedInput schema / properties / environment / description
      Previous value: -"Optional environment label (default from MCP_ENVIRONMENT)"New value: +"Deployment environment label (e.g. \"production\", \"staging\"). Defaults to MCP_ENVIRONMENT if set."
    • changedInput schema / properties / expires_at / description
      Previous value: -"Optional ISO timestamp override"New value: +"Custom expiration time in ISO 8601 format (e.g. \"2026-06-17T00:00:00Z\"). Defaults to 7 days from now if omitted."
    • changedInput schema / properties / session_id / description
      Previous value: -"Session trace id"New value: +"Unique identifier for the current session/conversation. Used to group related memories together."
    • changedInput schema / properties / tags / description
      Previous value: -"Optional tags list"New value: +"Categorization labels for filtering (e.g. [\"decision\", \"architecture\", \"bugfix\"])"
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description alone must disclose behavior. It reveals auto-expiration (7 days or custom), but does not mention idempotency, side effects, size limits, or what happens on insertion (e.g., duplicate handling). Adequate but not exhaustive.

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?

Four sentences, each adding value: purpose, use cases, default behavior, and alternative. Front-loaded with core action, no fluff. Ideal structure.

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?

No output schema exists, so description should explain what the tool returns (e.g., success indication, memory ID). It does not. Also missing details on error conditions or how inserted memories can be accessed later. Functional but incomplete for a 7-parameter tool.

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 86%, so the schema already explains most parameters. The description adds minor context (e.g., body used for semantic search, agent_body defaults to server profile). This is baseline useful but not enhancing 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's purpose: storing short-term demo memories with auto-expiration. It specifies the resource (demo.memories) and provides specific use cases (observations, decisions, session notes). This effectively distinguishes it from siblings like memory_ingest for permanent storage.

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 advises to use for ephemeral context, and explicitly names memory_ingest as the alternative for permanent knowledge. It also explains default expiration and custom expires_at. Could compare more broadly with other siblings, but key guidance is strong.

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