JauMemory MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

add_to_collection

Add a memory to a collection to keep related information organized. Group memories for efficient retrieval across conversations.

Instructions

Add a memory to a collection.

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": {
      "collection_id": "<collection_id>",
      "memory_id": "<memory_id>"
    },
    "name": "add_to_collection"
  }
}

Input Schema

Name	Required	Description	Default
`collection_id`	Yes	UUID of the collection
`memory_id`	Yes	ID of the memory to add

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3May 31, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosure, but it says nothing about behavioral traits such as whether this is a reversible operation, whether it requires certain permissions, what happens if the memory is already in the collection, or if the collection must exist. This is severely lacking for a mutation tool.

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, short sentence that is perfectly front-loaded and contains no extraneous words. Every word earns its place, delivering the core purpose succinctly.

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 simplicity of the tool (2 required parameters, no output schema, no nested objects), the description is minimally adequate but fails to address obvious contextual gaps like error handling, side effects, or relationship to sibling tools.

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 coverage (100%) with descriptions for both parameters: memory_id and collection_id. The description adds no additional meaning beyond what the schema already provides, earning the baseline score of 3.

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 the action ('add'), the resource type ('memory'), and the target ('collection'), effectively distinguishing it from sibling tools like 'remove_from_collection' and 'create_collection'. The verb-resource combination is specific and unambiguous.

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 like 'remove_from_collection', 'create_collection', or search tools. There is no mention of prerequisites, error conditions, or constraints (e.g., memory must exist, collection must exist, duplicate handling).

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