Skip to main content
Glama
Sign In
omni-mcp-server

omni-mcp-server

by bitofacoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memory_store

Save key information, preferences, or context to persistent memory for retrieval in future conversations.

Instructions

Save a note, preference, or piece of context to persistent memory so it can be recalled in future conversations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>",
      "content": "<content>"
    },
    "name": "memory_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesA unique, descriptive identifier for this memory (e.g., "user_project_goals", "react_preferences"). Keep it snake_case.
contentYesThe detailed content you want to remember.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so the description must fully cover behavioral traits. It mentions 'persistent memory' but omits details like overwrite behavior, size limits, or data retention, which are important for an agent to anticipate side effects.

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?

Single, well-formed sentence that directly conveys the tool's purpose. No fluff or unnecessary detail.

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?

For a simple tool with 2 parameters and no output schema, the description is adequate but lacks behavioral context (e.g., overwrite rules). Could be more informative given the absence of annotations.

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 100%, so the baseline is 3. The description adds a hint about snake_case key naming but otherwise repeats schema info. No extra meaning for content parameter beyond 'detailed content'.

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 saves notes, preferences, or context to persistent memory, which is a specific write operation. It distinguishes itself from siblings like memory_retrieve (read) and memory_list (list).

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?

No explicit instructions on when to use this tool vs. alternatives (e.g., system file write). The description implies use for persisting context, but lacks when-not or sibling comparisons.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools