Skip to main content
Glama

memory_get

Read-only

Read one stored memory in full by name, matching hyphens and underscores interchangeably to retrieve exact project context for agents.

Instructions

Read one memory in full. Names match file names; "-" and "_" are interchangeable.

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

Input Schema

NameRequiredDescriptionDefault
nameYesMemory name, e.g. feedback_testing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already indicate a read-only operation, and the description adds important behavior: it returns a single memory in full and treats '-' and '_' as interchangeable in names. It does not describe not-found handling, but that is a minor gap for a simple read 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 two short sentences with no wasted words. The core operation is front-loaded and the naming rule follows immediately.

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 one-parameter read tool with read-only annotations, the description covers the operation, return scope ('in full'), and key name-matching behavior. It could mention not-found behavior or explicit sibling alternatives, but nothing critical 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 complete, but the description adds meaning beyond the schema by saying names match file names and that '-' and '_' are interchangeable. That is useful resolution semantics for the single 'name' parameter.

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 states a specific verb and resource: 'Read one memory in full.' This clearly differentiates getting a single full memory from listing or recalling memories, although it does not explicitly name the sibling tools.

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?

It implies usage when the caller knows the memory name and needs the full content, but it does not explicitly say when to use this instead of memory_list or memory_recall. The usage context is understandable but left to inference.

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

This server cannot be deployed

Other Tools