Skip to main content
Glama

memory_get

Read-onlyIdempotent

Read a single memory together with its correction history and the source task, event, or file references so you can verify how a stored result or decision originated and changed.

Instructions

Read one memory and its correction history with source task/event/file references.

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

Input Schema

NameRequiredDescriptionDefault
task_idYes
memory_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful content scope by saying the result includes correction history and source task/event/file references, but it says nothing about behavior when the memory is missing or access is denied.

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?

It is a single, front-loaded sentence with no filler. Every element, including the correction history and source references, adds information.

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?

The tool is simple, has an output schema, and has annotations covering safety, so the description does not need to explain return format. However, with two required and completely undocumented parameters, the definition is not quite complete enough for an agent to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so neither task_id nor memory_id is documented in the schema. The description never mentions either parameter and does not explain how task_id scopes the lookup, leaving the parameter meanings to inference.

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 ('Read') and resource ('one memory'), and it scopes the return to a single memory plus correction history and source references. The word 'one' implicitly distinguishes it from search-style siblings like memory_search, though no sibling is named explicitly.

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 single-memory framing implies when to use it over a search tool, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. Usage is inferable rather than stated.

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