Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_memory_log

Append a milestone event to a durable, append-only timeline. Use for significant completions, decisions, or changes that need permanent record; entries cannot be edited or deleted, so log as finished facts.

Instructions

Mutating: appends a milestone event to the separate milestones table (not the memories table). event (required) is the free-text description of what happened (e.g. "deployed v1.0"); project and tags (comma-separated) are optional. Milestones are append-only — they cannot be edited or deleted, so phrase entries as finished facts. Returns {"logged", "project"}. Use for significant completions, decisions, or changes worth a durable timeline; use sassy_memory_remember for ongoing state you will later update, and sassy_memory_milestones to read the milestone history back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
eventYes
projectNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
loggedYes
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.1
    • addedOutput schema / properties / logged
      Added value: +{
+  "title": "Logged",
+  "type": "string"
+}
    • addedOutput schema / properties / project
      Added value: +{
+  "title": "Project",
+  "type": "string"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "logged",
+  "project"
+]
    • changedOutput schema / title
      Previous value: -"sassy_memory_logOutput"New value: +"LogResult"
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false), the description discloses crucial behavioral constraints: the operation is append-only, entries cannot be edited or deleted, and the return value is {'logged', 'project'}. This gives the agent a clear model of side effects and persistence semantics.

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 serves a purpose: mutation flag, target table, parameter semantics, append-only constraint, return value, and usage alternatives. It is front-loaded with the most critical facts and contains no filler.

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?

With only 3 simple parameters and an output schema present, the description still goes beyond the minimum by covering mutation behavior, storage target, immutability, return shape, parameter details, and sibling routing. 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%, but the description fully compensates: it explains event is a required free-text description with an example, and that project and tags are optional with tags being comma-separated. Every parameter is given semantic meaning beyond raw schema titles.

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 ('appends'), a specific resource ('milestones table'), and explicitly distinguishes it from the 'memories table'. It also names the intended use case ('significant completions, decisions, or changes'), leaving no ambiguity about what this tool does.

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 provides when-to-use guidance ('Use for significant completions, decisions, or changes worth a durable timeline') and names exact alternative tools for different scenarios (sassy_memory_remember for ongoing state, sassy_memory_milestones for reading history). This routes the agent to the correct sibling without extra inference.

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