Sutra

Search Sutra memory

search_memory

Read-onlyIdempotent

Return memories matching case-insensitive keywords and optional cluster filters.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Short, specific keywords describing the memories to find.
`top_k`	No	Maximum number of matching memories to return.
`cluster`	No	Optional cluster name to restrict the search.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`memories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 2, 2026

changedInput schema / properties / cluster / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 50,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9-]{1,50}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / cluster / description

Added value: +"Optional cluster name to restrict the search."

addedInput schema / properties / query / description

Added value: +"Short, specific keywords describing the memories to find."

addedInput schema / properties / query / maxLength
```
Added value: +2000
```
addedInput schema / properties / query / minLength
```
Added value: +1
```

addedInput schema / properties / top_k / description

Added value: +"Maximum number of matching memories to return."

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "memories": {
+    "items": {
+      "properties": {
+        "cluster": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "content": {
+          "type": "string"
+        },
+        "created_at": {
+          "type": "string"
+        },
+        "importance": {
+          "type": "integer"
+        },
+        "source_agent": {
+          "type": "string"
+        },
+        "tags": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "content",
+        "source_agent",
+        "importance",
+        "created_at",
+        "tags"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "memories"
+]
```

First observedSep 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so safety is covered. The description adds the useful behavioral detail that matching is case-insensitive, but says nothing about ranking, relevance, or how results are ordered.

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?

A single front-loaded sentence with zero waste. The core action and its modifiers are stated 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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The only real gap is routing guidance versus sibling retrieval tools, which is minor for a straightforward search.

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 100%, so the schema fully documents query, top_k, and cluster. The description restates keywords and cluster filters without adding format or syntax meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb (return/search) and resource (memories) with scope detail (case-insensitive keywords, cluster filters). This distinguishes it from read-only siblings like get_cluster or list_clusters, though it doesn't explicitly name an alternative search path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this over alternatives such as read_context or get_cluster, nor any prerequisites or exclusions. The agent must infer the search-vs-fetch distinction from the name alone.

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

All Sutra tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?