Skip to main content
Glama
VelixarAi

Velixar MCP Server

Official
by VelixarAi

velixar_store

Store important facts, decisions, user preferences, and project context for long-term retrieval. Memories persist across sessions with automatic chunking and duplicate detection.

Instructions

Store a memory for later retrieval. Use for important facts, decisions, user preferences, project context, or anything worth remembering long-term. Memories are workspace-scoped and persist across sessions. Long content is automatically chunked; max 50,000 characters (larger is rejected with a 400 before embedding — split it or chunk client-side). DEDUP (before you call): exact byte-identical duplicates are always blocked server-side. If this content may overlap semantically with existing memories, either velixar_search first or pass check_duplicate:true to run a near-duplicate check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags for categorization
tierNoMemory tier: 0=pinned, 1=session, 2=semantic (default), 3=org
atomicNoStore as a single unit — never split into chunks. Use for poems, quotes, structured data that must stay whole.
sourceNoProvenance label (e.g., "user-stated", "derived-from-analysis")
contentYesThe memory content to store (max 50,000 chars; longer is rejected before embedding). Long content is chunked automatically.
source_idsNoDERIVATION lineage — the memory IDs this new memory was reasoned/built FROM (e.g. you learned context B from context A). An explicit, directed "derived-from" edge, DISTINCT from semantic similarity and from the temporal previous-memory chain. Omit for an origin memory (learned fresh, no prior context). Query the resulting graph with velixar_lineage.
check_duplicateNoExact byte-identical duplicates are ALWAYS blocked server-side regardless of this flag (existing id returned, nothing written). Set true to ADDITIONALLY run a near-duplicate similarity check — advisory: near-dupes above dedup_threshold warn but still store.
dedup_thresholdNoSimilarity threshold for duplicate detection (default: 0.95). Only used when check_duplicate is true.
quarantine_zoneNoOptional quarantine zone ID. Memory will only be visible to zone members.
Behavior5/5

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

No annotations provided, but the description fully discloses key behaviors: workspace-scoping, persistence, automatic chunking, exact-duplicate blocking, near-duplicate option, tier system, and max size enforcement.

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?

Well-structured with front-loaded purpose and grouped details. Slightly verbose but every sentence adds value; could trim a few words.

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 complexity (9 params, no output schema), the description covers all critical aspects: chunking, dedup, scope, parameter usage, and result behavior (existing ID returned). No gaps.

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?

Schema coverage is 100%, but the description adds significant context beyond the schema: explains source_ids as derivation lineage, check_duplicate for near-duplicates, atomic for no-split, tier meanings, quarantine_zone visibility.

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 'Store a memory for later retrieval' and enumerates specific use cases (facts, decisions, preferences, etc.). It distinguishes from siblings by focusing on storage vs. search, delete, etc.

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

Usage Guidelines5/5

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

Explicitly advises when to use (store) and when to check duplicates first, even naming velixar_search as an alternative. Warns about size limits and automatic chunking.

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/VelixarAi/velixar-mcp-server'

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