Memory MCP

memory_profile

Manage user preferences and settings with get, set, and list actions. Store structured key-value data such as preferred language, editor, or timezone to personalize agent responses.

Instructions

Key-value store for user preferences and settings. Use this for structured data like preferred_language, editor, timezone — not for general knowledge (use memory_add for that).

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

Input Schema

Name	Required	Description
`key`	No	Required for get and set
`value`	No	Required for set
`action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Sep 6, 2026

TDQS

A4.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only describes the tool's domain, not what happens on set (overwrite semantics), whether get/list have side effects, or any persistence or authorization behavior. The action enum supplies the operations but not their behavioral implications.

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?

A single sentence with front-loaded purpose, concrete examples, and an explicit alternative. No filler or repetition of schema details.

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

Completeness4/5

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

Given the low complexity, the schema covers required parameters and allowed actions, and the description covers selection criteria. A minor gap is the lack of output or return information for the list action, but the action name and key-value domain make this largely self-evident.

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?

The schema already documents key ('Required for get and set') and value ('Required for set'), and the action enum lists valid actions. The description adds value by giving example keys and clarifying that values are structured preferences/settings, which helps an agent construct valid key/value pairs.

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 identifies the tool as a key-value store for user preferences and settings and gives concrete example keys (preferred_language, editor, timezone). It also distinguishes the target data type from general knowledge and names memory_add as the alternative, so an agent can tell it apart from siblings.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool ('Use this for structured data...') and when not to ('not for general knowledge'), directly naming memory_add as the alternative. This is specific and actionable, covering both positive and negative selection criteria.

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

Deploy Server