Skip to main content
Glama
Sign In
Memory Box MCP Server

Memory Box MCP Server

by amotivv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

save_memory

Store text or raw content as a memory in the Memory Box MCP Server, organizing it into specific buckets with structured metadata for easy retrieval and semantic understanding.

Instructions

Save a memory to Memory Box

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": {
      "text": "<text>"
    },
    "name": "save_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucket_idNoThe bucket to save the memory to (default: "General")
raw_contentNoRaw content for processing (alternative to text)
reference_dataNoStructured metadata for memory storage
source_typeNoType of memory source (default: 'llm_plugin')
textYesThe memory content to save (either text OR raw_content required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Save a memory' implies a write operation, but the description doesn't cover critical aspects like required permissions, whether this creates new or overwrites existing memories, error conditions, or response format. For a mutation tool with complex parameters, this leaves significant gaps in understanding its behavior.

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?

The description is extremely concise with a single sentence: 'Save a memory to Memory Box'. It's front-loaded and wastes no words, though this brevity contributes to gaps in other dimensions. Every word serves a purpose in stating the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters with nested objects, no output schema, and no annotations), the description is insufficient. It doesn't explain what constitutes a 'memory', how saving interacts with the system, what happens on success/failure, or how it relates to sibling tools. For a write operation with rich input structure, more context is needed to use it effectively.

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 100%, providing detailed documentation for all parameters. The description adds no parameter information beyond what's in the schema, so it doesn't enhance understanding of semantics. However, with comprehensive schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Save a memory to Memory Box' clearly states the action (save) and resource (memory to Memory Box), but it's quite generic. It doesn't specify what a 'memory' is in this context or differentiate this tool from sibling tools like 'update_memory' or 'create_bucket'. The purpose is understandable but lacks specificity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With siblings like 'update_memory', 'create_bucket', and 'search_memories', the description offers no context on prerequisites, appropriate scenarios, or distinctions. The agent must infer usage from the tool name and parameters alone.

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

Related Tools