Skip to main content
Glama
yamantaka520

agent-memory-os

by yamantaka520

memory_share

Change the audience of a stored memory: share it with team, project, or agents, or revert to private. Only the owner can modify visibility.

Instructions

Change who can read an existing memory (share it, or make it private again).

    Use this to promote a note you already stored to your team/project so
    collaborators can recall it, or to lock it back down. Only the memory's OWNER
    may change its visibility. The change propagates over sync — sharing reaches
    teammates, and making it private retracts it. Returns the memory's `id` and new
    `visibility`, or an `{"error": ...}` object if it doesn't exist, isn't yours, or
    `share` is invalid.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shareNoNew audience: 'private' (owner only), 'global' (all agents), 'team' or 'team:<id>', 'project' or 'project:<id>', or 'agent:<id>'.private
memory_idYesId of the memory whose visibility you want to change.
Behavior5/5

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

With no annotations, description fully discloses ownership requirement, propagation over sync, effects of sharing/retracting, and error conditions (not found, not owner, invalid share). This is thorough 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.

Conciseness4/5

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

Description is front-loaded with purpose, then details. A few extra words could be trimmed, but overall efficient and well-structured for its length.

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

Completeness5/5

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

Given 2 parameters, no output schema, and no annotations, the description covers purpose, usage, parameters, behavioral nuances, and error responses. Nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100% and description adds value by explaining the 'share' parameter audience options with examples and clarifying the memory_id parameter's purpose. Slight redundancy with schema but beneficial context.

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 starts with a clear verb 'Change who can read' and resource 'existing memory', distinguishing it from siblings like memory_add or memory_update. It also gives synonyms 'share it, or make it private again' for added clarity.

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?

Explicitly states when to use: 'promote a note ... to your team/project' or 'lock it back down'. Also covers ownership prerequisite. Lacks explicit when-not-to-use or alternatives, but context is sufficiently clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yamantaka520/Agent-Memory-OS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server