Skip to main content
Glama
Sign In
Hystersis MCP Server

Hystersis MCP Server

by Himan-D
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

add_memory

Stores user preferences, facts, or instructions as persistent memories for recall across sessions.

Instructions

Add a new persistent memory or fact to Hystersis. Use this when the user shares a preference, fact, or instruction that should be remembered across sessions.

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": {
      "content": "<content>"
    },
    "name": "add_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe content of the memory or fact
user_idNoOptional user ID to associate the memory with
categoryNoCategory of the memory (e.g., preference, fact, code_style)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only mentions 'persistent.' It lacks information on side effects (e.g., overwrite behavior, idempotency), error handling, permissions, or rate limits. This is insufficient for a write operation.

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, consisting of two short sentences with no waste. The action and usage guideline are front-loaded, making it easy to scan.

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?

Given the tool's simplicity (3 parameters, no output schema, no annotations), the description covers purpose and usage adequately but omits what the tool returns or confirms success. More context on the response would improve completeness.

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 input schema provides 100% coverage with clear descriptions for all three parameters. The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Add') and resource ('persistent memory or fact') to clearly state the tool's purpose. It distinguishes from sibling tools like create_entity and search_memories, as adding memory is a distinct action.

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?

The description provides an explicit usage scenario: 'Use this when the user shares a preference, fact, or instruction that should be remembered across sessions.' It does not include exclusions or alternatives, but the context is clear enough for typical use.

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