codemem

Overview Schema Source Related Servers Discussions Admin

memory_get_observations

Read-only

Fetch stored memories by exact IDs, applying filters for kind, project, visibility, scope, and trust. Missing or filtered-out IDs are omitted, returning only relevant existing records.

Instructions

Fetch multiple memories by exact IDs. Does not inherit the default project. Missing or filtered-out IDs are omitted from results, not reported as not_found.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	Yes	Memory IDs to fetch
`kind`	No	Filter by memory kind
`project`	No	Filter by project scope (matches sessions.project)
`scope_id`	No	Filter by a single sharing domain scope_id
`trust_bias`	No
`visibility`	No
`personal_first`	No
`ownership_scope`	No
`exclude_actor_ids`	No
`exclude_scope_ids`	No	Sharing domain scope_ids to exclude
`include_actor_ids`	No
`include_scope_ids`	No	Sharing domain scope_ids to include
`exclude_visibility`	No
`include_visibility`	No
`exclude_trust_states`	No
`include_trust_states`	No
`exclude_workspace_ids`	No
`include_workspace_ids`	No
`widen_shared_when_weak`	No
`exclude_workspace_kinds`	No
`include_workspace_kinds`	No
`widen_shared_min_personal_score`	No
`widen_shared_min_personal_results`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.44.2Sep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "items": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "body_text": {
+            "type": "string"
+          },
+          "confidence": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "id": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "metadata_json": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "session_id": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "title": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "kind",
+          "title",
+          "body_text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds valuable behavioral context: it does not inherit the default project, and missing/filtered-out IDs are silently omitted rather than reported as not_found. This goes beyond the annotations and helps an agent predict result behavior.

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 sentences, front-loaded with the primary action and resource, followed by two critical behavioral caveats. No wasted words; every sentence earns its place.

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 has 23 parameters and an output schema, and the description covers the core fetch-by-IDs behavior plus two important caveats. However, with 26% schema coverage and many filter parameters, an agent may not know how filters interact with the ID-based fetch or what the output schema contains. The description is adequate for the primary use case but incomplete for advanced filtering scenarios.

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 only 26%, so the description carries some burden for parameter meaning. The description clarifies the key 'ids' parameter semantics (exact IDs, omission behavior) and the 'project' parameter (does not inherit default). However, most of the 23 parameters remain undocumented in both schema and description, so the description only partially compensates for the low coverage.

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 ('Fetch') and resource ('multiple memories by exact IDs'), and distinguishes itself from a default-project behavior. It is clear enough to separate from siblings like memory_get (singular) and memory_search (query-based), though it does not explicitly name those siblings.

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: use this when you have exact memory IDs and want to fetch multiple memories. It notes that it does not inherit the default project, which is a useful context signal. However, it does not explicitly state when to prefer this over memory_get or memory_search, nor does it mention alternatives.

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

Deploy Server