Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_memory_milestones

Read-onlyIdempotent

Review project milestones and decisions in reverse chronological order. Filter by project and set limit to retrieve the newest completion events, including tags and timestamps.

Instructions

Read-only: reads back milestone events written by sassy_memory_log, newest first. project (default "") is an optional substring filter on the project field. limit (default 20, hard-capped at 100) controls how many of the newest entries are returned. Returns {"count", "milestones"} with each entry carrying id, event, project, tags, and timestamp. Use to review the timeline of completions and decisions for a project or overall; use sassy_memory_search to find arbitrary memory records, which live in a different table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
projectNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
milestonesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.15.1
    • addedOutput schema / $defs
      Added value: +{
+  "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 / count
      Added value: +{
+  "title": "Count",
+  "type": "integer"
+}
    • addedOutput schema / properties / milestones
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/Milestone"
+  },
+  "title": "Milestones",
+  "type": "array"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "count",
+  "milestones"
+]
    • changedOutput schema / title
      Previous value: -"sassy_memory_milestonesOutput"New value: +"MilestonesResult"
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context beyond that: the hard cap of 100 on limit, the 'newest first' ordering, and the return format with specific fields. It also notes the data lives in a different table than search, which is useful operational context. No contradictions.

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 with the most important fact ('Read-only') and packs each sentence with purpose. It covers behavior, parameters, return format, and usage in three sentences with zero fluff.

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 two-parameter, read-only tool with an output schema, the description covers all necessary aspects: what it does, how to filter and limit, the return structure, and when to use an alternative. Nothing essential is missing for an agent 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?

The schema provides only types and defaults with no descriptions (coverage 0%), so the description must fully compensate. It does: project is explained as an optional substring filter with default '', and limit is explained as controlling count of newest entries, with default 20 and a hard cap at 100. This adds significant meaning beyond the raw schema.

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 states a specific verb ('reads back'), a specific resource ('milestone events written by sassy_memory_log'), and an ordering ('newest first'). It explicitly distinguishes from sassy_memory_search by noting they operate on different tables, so an agent can tell them apart without opening schemas.

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?

It explicitly says 'Use to review the timeline of completions and decisions' and then gives the alternative: 'use sassy_memory_search to find arbitrary memory records, which live in a different table.' This provides clear when-to-use and when-not-to-use guidance, naming the sibling directly.

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