Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_memory_search

Read-onlyIdempotent

Search memories by literal keyword, tags, project, or priority to locate a record when you don't know its exact key. Returns matching full records, most recent first.

Instructions

Read-only keyword search over all memories using substring matching (not semantic: the query must appear literally in the key or value). query (default "") is free text matched against keys and values; tags is a comma-separated list where each tag must appear in the record's tags; project is a substring match on the project field; priority is an exact match (critical|high|normal|low). All filters combine with AND. Results are ordered by most recently updated first and capped at 50 (limit defaults to 20; an empty query returns everything). Returns {"count", "results"} as full records. Use when you know what to find but not its key; use sassy_memory_recall for an exact key and sassy_memory_context for the standard session-start bundle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
limitNo
queryNo
projectNo
priorityNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.15.1
    • addedOutput schema / $defs
      Added value: +{
+  "MemoryRecord": {
+    "properties": {
+      "access_count": {
+        "title": "Access Count",
+        "type": "integer"
+      },
+      "created_at": {
+        "title": "Created At",
+        "type": "number"
+      },
+      "key": {
+        "title": "Key",
+        "type": "string"
+      },
+      "priority": {
+        "title": "Priority",
+        "type": "string"
+      },
+      "project": {
+        "title": "Project",
+        "type": "string"
+      },
+      "tags": {
+        "title": "Tags",
+        "type": "string"
+      },
+      "updated_at": {
+        "title": "Updated At",
+        "type": "number"
+      },
+      "value": {
+        "title": "Value",
+        "type": "string"
+      }
+    },
+    "required": [
+      "key",
+      "value",
+      "tags",
+      "priority",
+      "project",
+      "created_at",
+      "updated_at",
+      "access_count"
+    ],
+    "title": "MemoryRecord",
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / count
      Added value: +{
+  "title": "Count",
+  "type": "integer"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / results
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/MemoryRecord"
+  },
+  "title": "Results",
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "count",
+  "results"
+]
    • changedOutput schema / title
      Previous value: -"sassy_memory_searchOutput"New value: +"SearchResult"
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds valuable behavior beyond that: substring semantics, AND-combination of filters, ordering by most recent, the 50-result cap, empty-query behavior, and the return shape. No contradiction with annotations.

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 dense but every sentence adds operational information. It front-loads the core read-only substring behavior, then systematically walks through the parameters, then gives routing guidance. No filler or redundancy.

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?

For a tool with five optional parameters, no required parameters, and an output schema, the description fully covers filter semantics, combination logic, ordering, result cap, defaults, and empty-query behavior. An agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and succeeds. It explains query matching against keys and values, tags as comma-separated AND-matching, project as substring, priority as exact match, and limit's default and cap. Every parameter's semantics are covered.

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?

The description names a specific operation ('Read-only keyword search over all memories') and clarifies that matching is literal substring, not semantic. It also explicitly distinguishes itself from sassy_memory_recall and sassy_memory_context at the end, making the tool's identity 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?

The description states exactly when to use this tool ('when you know what to find but not its key') and names the alternatives for other cases: sassy_memory_recall for exact key lookup and sassy_memory_context for the session-start bundle. This is explicit usage guidance.

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