Skip to main content
Glama
Sign In
xmszm-memory

xmszm-memory

by xmszm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

initialize

Prepare a namespace with boot/personality memories for a new session, creating default identity and workflow memories. Idempotent: never overwrites existing memories.

Instructions

Initialize a namespace with v2.1 boot/personality memories. On a new session, call initialize(namespace, profile?) once if the namespace may be empty, then read(namespace, "system://boot") before answering. Idempotent: active existing memories are never overwritten. profile defaults to "assistant"; accepted profiles are "assistant" and "blank".

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": {
      "namespace": "<namespace>"
    },
    "name": "initialize"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoassistant creates default identity/principle/workflow memories; blank creates only minimal structural identity placeholders.assistant
namespaceYesUser namespace, e.g. admin or alice

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.8/5.0
Behavior3/5

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

The description discloses idempotency ('active existing memories are never overwritten'), which is useful behavioral context. However, it does not mention permissions, what happens to inactive memories, or any return behavior. Since there are no annotations, the description carries the full burden but only partially addresses safety and 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?

The description is three sentences, tightly written, and front-loaded with the core purpose. Every sentence adds practical information, including the workflow and idempotency.

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

Completeness4/5

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

Given the tool's simple two-parameter signature and absence of an output schema, the description covers the essential context: when to call it, what it does, its idempotency, and the profile options. It does not describe return values, but that is acceptable given the tool's initialization nature.

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?

The schema already provides full descriptions for both parameters (namespace and profile) with a default and enum for profile. The description adds minimal value by restating the default and accepted profiles, so it does not exceed the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states a specific action and resource: 'Initialize a namespace with v2.1 boot/personality memories.' This is a distinct operation from siblings like create or update, though it does not explicitly name alternatives.

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?

It provides explicit when-to-use guidance: 'On a new session, call initialize(namespace, profile?) once if the namespace may be empty, then read(namespace, "system://boot") before answering.' This gives a clear condition and sequence. It also notes idempotency, implying repeated calls are safe.

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