codemem

Overview Schema Source Related Servers Discussions Admin

memory_search_index

Read-only

Search stored memories by exact keywords, returning matching entries with IDs and titles. Use memory_get to expand selected entries.

Instructions

Keyword-search memories when you know exact terms or identifiers. Returns compact entries with IDs and titles, without bodies; expand selected IDs with memory_get or memory_get_observations.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Filter by memory kind
`limit`	No	Max results
`query`	Yes	Search query
`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": {
+          "created_at": {
+            "type": "string"
+          },
+          "id": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "metadata": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "score": {
+            "type": "number"
+          },
+          "session_id": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "kind",
+          "title",
+          "score",
+          "created_at",
+          "session_id",
+          "metadata"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate safety. It adds useful behavioral context: returns compact entries without bodies, and suggests follow-up expansion. However, it doesn't explain filtering semantics, trust_bias, or how the 24 parameters affect results, which would be valuable for a search tool with many filters.

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 core purpose and a clear follow-up action. Every word earns its place; no fluff or repetition of schema details.

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

Completeness2/5

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

Despite having an output schema, the tool has 24 parameters with only 29% schema coverage and no enums. The description does not explain the filtering model, trust/visibility semantics, or how to combine parameters. For a complex search tool, this is incomplete: an agent cannot reliably know what filters exist or how they interact.

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 only 29%, and the description does not compensate. It mentions query and the compact return format, but does not explain the many filter parameters (kind, project, scope_id, visibility, trust_bias, ownership_scope, include/exclude lists, widen_shared_*). With 24 parameters and most undocumented, the description leaves the agent guessing about how to construct effective searches.

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 clearly states the tool performs keyword search over memories and returns compact entries with IDs and titles, which distinguishes it from memory_get and memory_get_observations. It does not explicitly name sibling search tools like memory_search or memory_recent, but the focus on exact terms/identifiers and compact results gives reasonable differentiation.

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 says to use it when you know exact terms or identifiers, and tells the agent to expand selected IDs with memory_get or memory_get_observations. It does not explicitly say when not to use it or name alternative search tools like memory_search, but the guidance is clear enough for basic selection.

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

Deploy Server