Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_state_clear

DestructiveIdempotent

Permanently delete a tool's stored state, or wipe all state across the server. Requires exact 'YES' confirmation to prevent accidental data loss.

Instructions

Destructive and mutating: permanently deletes stored state from the persistent per-tool SQLite state store (tool_state.db in the SassyMCP home directory). Optional tool_name="": when given, deletes every key saved under that tool name; when empty, deletes ALL state for ALL tools across the server with no way to recover. Requires confirm='YES' (exact, case-sensitive) on every call, matching the sassy_permission privilege mutations and sassy_audit_clear. Use to reset a misbehaving tool's remembered state or to wipe the whole state store clean; read first with sassy_state_get and back up values with sassy_state_set if they matter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNo
tool_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": "",
+  "title": "Confirm",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds crucial context: 'permanently deletes', 'no way to recover', the exact confirm='YES' requirement, and that an empty tool_name wipes ALL state for ALL tools. This goes well beyond the structured annotations and fully discloses the dangerous behavior.

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?

Every sentence adds value: hazard first, then resource, parameter semantics, safety gate, and usage guidance. It is dense but efficient, and the most critical information (destructive, permanent) is front-loaded.

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 tool's destructive nature and optional parameters, the description covers all necessary aspects: what is deleted, how deletion scope changes, the confirmation requirement, and how to preserve data before calling. An output schema exists, so return-value documentation is not required.

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 coverage is 0%, yet the description fully explains both parameters: tool_name's behavior when given vs. empty, and confirm's exact-case requirement. It compensates perfectly for the lack of schema descriptions.

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-resource pair ('permanently deletes stored state') and clearly identifies the underlying store (per-tool SQLite state store), distinguishing it from sibling tools like sassy_state_get and sassy_state_set. It is absolutely clear what the tool does and how it differs from related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit use cases ('reset a misbehaving tool's remembered state or to wipe the whole state store clean') and advises reading with sassy_state_get and backing up with sassy_state_set first. It does not explicitly state when not to use it vs. alternatives, but the context is strong enough for an agent to decide.

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