Skip to main content
Glama
10CG

nexusm-mcp-server

by 10CG

nexus.memory_create

Persist structured memories—episodic events, semantic facts, procedural how-tos—when users request to remember information. Supports metadata tags and temporal validity.

Instructions

Persist a new memory. Use when user explicitly asks to 'remember X' or when storing structured facts (preferences, decisions, code snippets with language tag). Set memory_type to 'episodic' for events, 'semantic' for facts, 'procedural' for how-tos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
contentYes
memory_typeNosemantic
metadataNoFree-form structured tags (e.g., {language: 'python', tags: ['snippet', 'react-hooks']}). Use ≤ 10 keys, value length ≤ 200 chars (proposal §ai R2 D-8 cap; over-cap → InvalidParams).
valid_untilNo
valid_until_sourceNov6 US-035 temporal validity (backend ValidUntilSource Literal, 5 values, locked in proposal §R2.1). MCP client typically passes 'sdk_provided' (user-declared) or omits to let backend worker auto-extract. Any value outside the 5-enum is rejected at args parse stage with InvalidParams.
agent_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYes
created_atYes
conflict_resolutionNoIf v6 US-036 ConflictResolver is enabled (per-tenant feature flag), resolution_status echoed here. NULL when feature flag disabled. status enum locked to 9 values (migration 020 CHECK).
Behavior2/5

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

No annotations provided, so description must carry full behavioral burden. It only mentions persistence (a write operation) but lacks details on side effects, authentication, rate limits, or content restrictions beyond metadata constraints.

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?

Two sentences, front-loaded with the core action. No unnecessary words; every sentence adds value.

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?

Covers core purpose and key parameters adequately, but lacks details on content length limits, valid_until semantics, and expected return values despite output schema existence.

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 29%, meaning most parameters lack descriptions. The description adds value for memory_type (episodic/semantic/procedural mapping) and metadata (free-form tags), but does not elaborate on user_id, content, valid_until, or agent_id.

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 explicitly states 'Persist a new memory' and provides concrete usage scenarios (e.g., storing preferences, facts, code snippets). It distinguishes from siblings (retrieve, feedback, search) by focusing on creation.

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 gives clear guidance on when to use (e.g., 'when user explicitly asks to remember X') and maps memory_type to use cases. It does not explicitly exclude other scenarios, but the sibling list 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/10CG/nexusm-mcp-server'

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