Life Memory MCP

set_memory_sharing

Change a memory profile's visibility to private, unlisted, or public and control whether AI persona simulation is allowed. Requires the owner token to update sharing settings.

Instructions

Change whether a memory profile is private, unlisted, or public and whether AI persona simulation is allowed. Requires owner token.

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": {
      "profile": "<profile>",
      "owner_token": "<owner_token>",
      "visibility": "<visibility>",
      "consent_to_simulation": "<consent_to_simulation>"
    },
    "name": "set_memory_sharing"
  }
}

Input Schema

Name	Required	Description	Default
`profile`	Yes
`visibility`	Yes
`owner_token`	Yes
`consent_to_simulation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 12, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so the description carries the full behavioral burden. It discloses the auth requirement ('Requires owner token') but omits mutation semantics: whether changes are reversible, what happens to existing sharing state, any rate limits, or return format.

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?

Two sentences, front-loaded with the core action, then the prerequisite. No redundant or filler content.

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?

For a four-required-parameter mutation tool with no annotations and no output schema, the description is incomplete: it lacks parameter-level guidance, behavioral details, and usage context relative to siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains visibility values and consent_to_simulation, but the 'profile' and 'owner_token' parameters receive only implicit mention ('a memory profile', 'Requires owner token') with no details like expected format or ID source.

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?

States a specific verb 'Change' and resource 'memory profile' sharing settings, and enumerates the two dimensions (visibility and AI persona simulation consent). Distinguishes from siblings like create_memory_profile or save_memory which do not alter sharing settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the unique action, but no explicit when-to-use vs alternatives, and no prerequisites beyond the owner token requirement. Siblings such as create_memory_profile or load_memory_persona are not referenced.

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

Deploy Server