Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_memory_stats

Read-onlyIdempotent

Get a read-only summary of stored memories: total count, priority breakdown, milestones, and active projects. Use it to assess what is available before querying or starting a session.

Instructions

Read-only: reports aggregate health of the memory system. Takes no parameters. Returns {"total_memories", "by_priority" (counts keyed by priority level), "milestones" (total milestone count), "projects" (sorted list of distinct non-empty project names)}. Use to get an overview of how much is stored and how it is organized before deciding how to query; use sassy_memory_context to load the actionable session-start bundle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectsYes
milestonesYes
by_priorityYes
total_memoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.15.1
    • addedOutput schema / properties / by_priority
      Added value: +{
+  "additionalProperties": {
+    "type": "integer"
+  },
+  "title": "By Priority",
+  "type": "object"
+}
    • addedOutput schema / properties / milestones
      Added value: +{
+  "title": "Milestones",
+  "type": "integer"
+}
    • addedOutput schema / properties / projects
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Projects",
+  "type": "array"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / total_memories
      Added value: +{
+  "title": "Total Memories",
+  "type": "integer"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "total_memories",
+  "by_priority",
+  "milestones",
+  "projects"
+]
    • changedOutput schema / title
      Previous value: -"sassy_memory_statsOutput"New value: +"StatsResult"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already provide readOnly/idempotent/non-destructive hints, and the description adds meaningful behavioral detail: exact returned keys and their semantics, including counts keyed by priority and a sorted list of distinct non-empty project names. This goes beyond what annotations convey, though it does not discuss error behavior or scalability.

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 compact and front-loaded: read-only status and purpose come first, followed by return shape and usage guidance. Every sentence contributes, with no filler or repetition of schema details.

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 zero-parameter read-only stats tool with an output schema and complete annotations, the description covers the return contract, the organization of results, and when to choose an alternative. Nothing an agent needs to call it correctly 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 tool has zero parameters, so there is little to document; the description explicitly confirms 'Takes no parameters' and the schema is empty. This satisfies the baseline for parameter-less tools.

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 uses a precise verb ('reports') and resource ('aggregate health of the memory system'), then names the sibling it is not called for (sassy_memory_context). It clearly distinguishes itself from other memory tools by stating exactly what it returns.

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 states when to use the tool ('before deciding how to query') and names the alternative sassy_memory_context for a session-start bundle. This gives direct routing guidance with no ambiguity.

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