Exogram — Personal AI Agent & Workspace

update_memory_vault

Persist or supersede a personal fact, commitment, or preference in your encrypted Exogram memory vault.

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": "update_memory_vault"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes	The fact, preference, or commitment to persist.
`namespace`	No	Logical grouping or sphere ("work", "household", "personal", or "default").	default

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It mentions encryption and superseding, but does not disclose permissions, reversibility, conflict resolution, whether prior facts are overwritten, or response behavior 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 definition is a single front-loaded sentence with no filler; the key action and scope are immediately clear.

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?

For a simple two-parameter mutation tool, the schema handles parameter meaning well and the description states the core purpose. However, without annotations or an output schema, it leaves important operational context about superseding, overwriting, and usage relative to sibling memory tools unstated.

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%, with both content and namespace documented in the input schema. The description adds no parameter-level detail beyond the schema and does not mention namespace behavior.

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 uses a specific verb phrase, "Persist or supersede," and a clear resource, "personal fact, commitment, or preference," in an encrypted vault. It does not explicitly distinguish itself from sibling tools like store_memory or search_memory_vault.

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?

The use case is implied by "persist or supersede a personal fact, commitment, or preference," but there is no explicit guidance on when to choose this tool over store_memory or search_memory_vault, nor any when-not conditions.

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

All Exogram — Personal AI Agent & Workspace tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.