SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_memory_context

Read-onlyIdempotent

Loads all session-start context in one call: critical priorities, active tasks, blockers, recent memories, patterns, milestones. Optionally add project filter for project memories.

Instructions

Read-only: loads the standard session-start context bundle in one call. Call this at the START of every session. project (default "") is an optional substring filter that adds a project_memories section. Returns a dict with eight sections: critical (up to 10 priority-critical records), high_priority (up to 10), active_tasks (up to 10 tagged task-active), blockers (up to 10 tagged blocker), recent_memories (up to 10 most recently updated), project_memories (up to 15, only when project is given), patterns (up to 10 tagged pattern), and milestones (up to 5 newest). Use instead of issuing many separate searches at startup; use sassy_memory_search for targeted follow-up queries and sassy_memory_recall for one exact record.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`blockers`	Yes
`critical`	Yes
`patterns`	Yes
`milestones`	Yes
`active_tasks`	Yes
`high_priority`	Yes
`recent_memories`	Yes
`project_memories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.15.1Sep 18, 2026

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"
+  },
+  "Milestone": {
+    "properties": {
+      "event": {
+        "title": "Event",
+        "type": "string"
+      },
+      "id": {
+        "title": "Id",
+        "type": "integer"
+      },
+      "project": {
+        "title": "Project",
+        "type": "string"
+      },
+      "tags": {
+        "title": "Tags",
+        "type": "string"
+      },
+      "timestamp": {
+        "title": "Timestamp",
+        "type": "number"
+      }
+    },
+    "required": [
+      "id",
+      "event",
+      "project",
+      "tags",
+      "timestamp"
+    ],
+    "title": "Milestone",
+    "type": "object"
+  }
+}

addedOutput schema / properties / active_tasks

Added value: +{
+  "items": {
+    "$ref": "#/$defs/MemoryRecord"
+  },
+  "title": "Active Tasks",
+  "type": "array"
+}

addedOutput schema / properties / blockers

Added value: +{
+  "items": {
+    "$ref": "#/$defs/MemoryRecord"
+  },
+  "title": "Blockers",
+  "type": "array"
+}

addedOutput schema / properties / critical

Added value: +{
+  "items": {
+    "$ref": "#/$defs/MemoryRecord"
+  },
+  "title": "Critical",
+  "type": "array"
+}

addedOutput schema / properties / high_priority

Added value: +{
+  "items": {
+    "$ref": "#/$defs/MemoryRecord"
+  },
+  "title": "High Priority",
+  "type": "array"
+}

addedOutput schema / properties / milestones

Added value: +{
+  "items": {
+    "$ref": "#/$defs/Milestone"
+  },
+  "title": "Milestones",
+  "type": "array"
+}

addedOutput schema / properties / patterns

Added value: +{
+  "items": {
+    "$ref": "#/$defs/MemoryRecord"
+  },
+  "title": "Patterns",
+  "type": "array"
+}

addedOutput schema / properties / project_memories

Added value: +{
+  "items": {
+    "$ref": "#/$defs/MemoryRecord"
+  },
+  "title": "Project Memories",
+  "type": "array"
+}

addedOutput schema / properties / recent_memories

Added value: +{
+  "items": {
+    "$ref": "#/$defs/MemoryRecord"
+  },
+  "title": "Recent Memories",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "critical",
+  "high_priority",
+  "active_tasks",
+  "blockers",
+  "recent_memories",
+  "project_memories",
+  "patterns",
+  "milestones"
+]

changedOutput schema / title

Previous value: -"sassy_memory_contextOutput"New value: +"ContextResult"

First observedv0.1.0Jul 31, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds valuable context: it is a bulk loader, limits counts per section, and includes optional project filtering. It confirms the read-only nature and explains output structure, going beyond the bare annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loads the purpose and usage instruction, then details the output sections efficiently. Every sentence adds value, though it is slightly long due to enumerating sections, but that is essential for clarity.

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?

Given the single optional parameter, comprehensive annotations, and presence of an output schema, the description covers everything needed: when to call, what it returns, and alternatives. No critical information is missing.

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

Parameters4/5

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

The schema has 0% description coverage, so the description must compensate. It explains the 'project' parameter as an optional substring filter that adds a project_memories section, providing critical meaning that the schema lacks. This fully clarifies the parameter's role.

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 clearly states the tool loads a standard session-start context bundle in one call, specifies it is read-only, and enumerates the exact sections returned. It differentiates from siblings by naming sassy_memory_search and sassy_memory_recall as alternatives for different needs.

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 instructs to call at the START of every session, and provides clear when-not-to-use guidance by pointing to sassy_memory_search for targeted follow-ups and sassy_memory_recall for one exact record. This leaves no ambiguity about when to invoke this tool.

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

Deploy Server