Skip to main content
Glama
catfish-1234

sessionmem

by catfish-1234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

searchMemoryIndex

Read-onlyIdempotent

Search a compact memory index to find relevant session memories by topic, returning IDs, previews, kinds, dates, and scores; use it first for topic lookups before fetching full memory bodies.

Instructions

Search a compact memory index. Returns IDs, one-line previews, kinds, capture dates and scores. Start here for topic lookups, use memoryTimeline for nearby context, then getMemory for selected full bodies. Default limit 10, maximum 50. Does not update access counters. hasMore refers to the bounded candidate pool.

Input Schema

NameRequiredDescriptionDefault
tagsNo
limitNo
queryYes
scopeNo
scopeModeNo
includeHistoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.10.0
    • addedInput schema / properties / scope
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 160,
+      "minLength": 1,
+      "pattern": "^[^\\x00-\\x1f\\x7f]+$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedInput schema / properties / scopeMode
      Added value: +{
+  "enum": [
+    "filter",
+    "boost"
+  ],
+  "type": "string"
+}
  2. Addedv1.9.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavioral context beyond the annotations: it describes return fields, default and maximum limit, that access counters are not updated, and how hasMore relates to the bounded candidate pool. Annotations already cover read-only and idempotent behavior, and the description complements them well.

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?

The description is front-loaded, information-dense, and free of filler. Each sentence adds practical value about workflow, return shape, limits, or side effects.

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?

It covers the search workflow, return shape, limit defaults, and hasMore semantics, which is useful for a tool without an output schema. However, for a six-parameter tool with no schema descriptions, it leaves key parameters like tags, scope, scopeMode, and includeHistory unexplained.

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 the description must explain parameter meanings. It only clarifies limit (default 10, maximum 50) and implies query via "topic lookups"; tags, scope, scopeMode (filter vs boost), and includeHistory are not explained at all.

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 and resource: "Search a compact memory index." It also distinguishes the tool from memoryTimeline and getMemory by positioning it as the starting point for topic lookups and full-body retrieval.

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?

Explicitly routes the agent: "Start here for topic lookups, use memoryTimeline for nearby context, then getMemory for selected full bodies." This gives clear when-to-use guidance and names the relevant alternatives.

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

Deploy Server

Other Tools