Skip to main content
Glama
Sign In
Unified Memory MCP

Unified Memory MCP

by yksanjo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Get Memory

get_memory
Read-onlyIdempotent

Retrieve a specific active memory by its ID. Control access to sensitive memories with the include_sensitive parameter.

Instructions

Fetch one active memory by id. Sensitive memories are hidden unless include_sensitive is true.

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": {
      "id": "<id>"
    },
    "name": "get_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
include_sensitiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds value by disclosing that sensitive memories are hidden by default and require the include_sensitive flag to be visible, which is beyond annotation details.

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 concise sentences with no fluff. Every sentence provides essential information: what the tool does and a key behavioral condition.

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 tool's simplicity (fetch by id) and the presence of annotations covering safety, the description is largely complete. It covers the main behavioral nuance (sensitive memories) but could mention error handling or id format. No output schema exists, so return values are not detailed.

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?

The schema has 0% description coverage, so the description carries the burden. It explains the effect of 'include_sensitive' but does not describe the 'id' parameter beyond its implied role. This adds some value but leaves the id parameter undocumented.

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 clearly states the verb 'Fetch', the resource 'one active memory', and the unique identifier 'by id'. It is specific and distinguishes this tool from siblings like list_memories or search_memory.

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?

The description provides clear context on when to use the include_sensitive parameter ('Sensitive memories are hidden unless include_sensitive is true'). It does not explicitly mention when not to use the tool or alternatives, but the guidance is sufficient.

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