Skip to main content
Glama
Sign In
Preference Memory MCP

Preference Memory MCP

by efficjump
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_get

Read-onlyIdempotent

Retrieve a specific preference memory using its unique identifier. Access saved user preferences for review or verification.

Instructions

Read one memory by its opaque identifier.

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

Input Schema

NameRequiredDescriptionDefault
memory_idYes

Output Schema

NameRequiredDescriptionDefault
foundYes
memoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already convey readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the retrieval context ('by its opaque identifier'), which is complementary and does not contradict annotations.

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?

The description is very short (8 words) and front-loads the core action. It could include more detail without becoming verbose, but it is efficient and avoids fluff.

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?

For a simple get-by-ID tool with a single parameter and an existing output schema, the description is adequate. It does not cover error cases (e.g., missing memory) but the output schema likely handles that.

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 0%, so the description carries the burden. It adds 'opaque identifier' context for the memory_id parameter, but does not explain its format, origin, or constraints beyond the schema (e.g., maxLength).

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 uses a specific verb ('Read') and resource ('one memory') with access method ('by its opaque identifier'), clearly distinguishing it from sibling tools like memory_recall (recalls multiple) or memory_remember (writes).

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 description implies usage when an opaque identifier is available, but does not explicitly state when to use this tool versus alternatives like memory_observe or memory_resolve. No exclusions or context are provided.

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

Deploy Server

Other Tools