Skip to main content
Glama
Sign In
memory_plus

memory_plus

by cx2002302-lang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

svm_store

Store structured visual memory blocks with unique keys and values for persistent AI agent recall.

Instructions

Store a memory block in SVM (Structured Visual Memory)

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>",
      "value": "<value>"
    },
    "name": "svm_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesUnique key for the memory block
valueYesContent/value of the memory block
slot_idNoOptional slot/group identifier
tenant_idNoOptional tenant ID (default: default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as idempotency, overwrite behavior, or side effects of storing. The agent is left to infer critical details.

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 a single, efficient sentence with no redundant words. Every word contributes to stating the core purpose.

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?

The description lacks critical context such as return values, storage behavior (e.g., update vs. create), and any constraints. Given no output schema and four parameters, more completeness is needed.

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%, with each parameter described in the schema. The tool description adds no additional meaning beyond what is already in the structured data, meeting the baseline expectation.

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 verb 'Store' and the resource 'memory block in SVM', and the acronym SVM is expanded. This distinguishes it from sibling tools like svm_recall (retrieve) and svm_forget (delete).

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 on when to use this tool vs. alternatives. It only implies storage usage without specifying conditions or exclusions.

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