Nexus Catalyst

Get full memory detail

get_memory_detail

Read-onlyIdempotent

Fetches the full stored content of one memory, by the memory_id returned from a search.

The second half of the recall → detail pattern: recall_context and search_memories return summaries truncated to 150 tokens, and this returns the complete preserved conversation content behind one of them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`memory_id`	Yes	The memory_id returned by recall_context or search_memories

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No
`error`	No	Present when the call did not succeed. An object carries `type` and `message` (and often a `timestamp`); Utils.formatError bodies set it to `true` with the reason in the top-level `message`.
`message`	No
`success`	No
`timestamp`	No	Unix epoch (milliseconds on most rows, seconds on legacy rows) or an ISO-8601 string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The full memory on success. Not found / not permitted returns `{ error: true, message, timestamp }` with no `success` key.",
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "properties": {
+        "artifact_url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "attribution": {
+          "description": "Present only alongside shared_by."
+        },
+        "client_project": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "company_client": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "context": {
+          "description": "The full stored context.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "context_summary": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "conversation_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "detail_id": {
+          "type": "string"
+        },
+        "detail_omitted": {
+          "description": "Fields left out of this response and why (see detail_omitted_reason).",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "detail_omitted_reason": {
+          "type": "string"
+        },
+        "extended_attributes": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "memory_id": {
+          "type": "string"
+        },
+        "persona": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "preserved_code": {
+          "description": "Code spans preserved verbatim from the original context.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "preserved_data": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "shared_by": {
+          "description": "Present only on a teammate's team-visible memory."
+        },
+        "summary": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timestamp": {
+          "description": "Unix epoch (milliseconds on most rows, seconds on legacy rows) or an ISO-8601 string.",
+          "type": [
+            "number",
+            "string",
+            "null"
+          ]
+        },
+        "user_query_full": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "error": {
+      "description": "Present when the call did not succeed. An object carries `type` and `message` (and often a `timestamp`); Utils.formatError bodies set it to `true` with the reason in the top-level `message`.",
+      "type": [
+        "object",
+        "boolean",
+        "string"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "timestamp": {
+      "description": "Unix epoch (milliseconds on most rows, seconds on legacy rows) or an ISO-8601 string.",
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the key behavioral context that this returns complete preserved content rather than truncated summaries, which clarifies output expectations beyond the schema. No contradictions found.

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 first sentence is crisp and action-oriented, and the second paragraph adds useful pattern context without redundancy. The description is not bloated; it front-loads the core action and then provides the sibling contrast. A minor nit is the slight repetition of the parameter origin in both sentences.

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

Completeness5/5

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

The tool has only one parameter, a clear purpose, and an output schema (per context signals) so return format is not the description's burden. The description explains the tool's role in the recall→detail pattern and its relationship to siblings, which is complete for an agent to call it correctly.

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 single parameter memory_id is fully described in the schema ('The memory_id returned by recall_context or search_memories'), and the description reiterates the same source. With 100% schema coverage, the description adds no new semantic value beyond the schema, so the baseline of 3 is appropriate.

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?

States a specific verb 'fetches' and a precise resource 'full stored content of one memory', and explicitly names the parameter (memory_id). It distinguishes itself from siblings recall_context and search_memories by contrasting their 150-token truncation with its complete content, making the tool's purpose unambiguous.

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?

Directly states the usage pattern: 'by the memory_id returned from a search' and identifies the siblings it complements ('recall_context and search_memories return summaries... this returns the complete...'). This gives the agent a clear when-to-use instruction and names alternatives, leaving nothing to inference.

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

All Nexus Catalyst tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?