JauMemory MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

create_collection

Create a new collection to organize memories by grouping related items together, with optional description and initial memory IDs.

Instructions

Create a new collection for organizing memories.

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

Input Schema

Name	Required	Description
`name`	Yes	Name of the collection
`description`	No	Description of the collection (optional)
`memory_ids`	No	Initial memory IDs to add to the collection (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3May 31, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. The description only indicates a mutation ('create') but fails to mention critical behavioral traits such as uniqueness constraints on 'name', idempotency, error conditions (e.g., duplicate name), required permissions, or return value. This is insufficient for an agent to safely invoke the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but overly brief. It lacks structure and fails to earn its place by omitting necessary details. A description this short should be packed with key information, but it only states the obvious.

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 (3 parameters, creation operation, no output schema, no annotations, and many sibling collection tools), the description is severely incomplete. It does not explain what happens on success, error states, or how this tool fits into the collection workflow. An agent would need to infer too much from the name alone.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions. The phrase 'for organizing memories' provides slight context but does not enhance understanding of the parameters themselves.

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 ('create') and the resource ('collection') with a hint of purpose ('for organizing memories'). It is not a tautology and the verb+resource combination is specific. However, it does not distinguish this tool from sibling tools like 'add_to_collection' or 'update_collection', which operate on existing collections.

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 (e.g., list_collections, get_collection, add_to_collection). There are no prerequisites, conditions, or exclusions mentioned. The description is entirely silent on usage context.

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