Skip to main content
Glama
privacyscrubber-mcp

privacyscrubber-mcp

Purge In-Memory Session Token Mappings (ZTDS RFC v1.0)

ztds_reset_session
DestructiveIdempotent

Irreversibly zeroizes volatile in-memory token mappings for one session or all active sessions, removing residual surrogate-to-PII links from RAM.

Instructions

Irreversibly zeroizes volatile in-memory surrogate token mappings for a specific sessionId or all active sessions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ztds_reset_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdNoOptional session identifier to purge. Omit or pass empty string to clear all active sessions in RAM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=true, so the safety profile is covered. The description adds the genuinely useful nuance that the destruction is irreversible and confined to volatile RAM (nothing persisted is affected), but it omits the post-condition an agent needs: that existing surrogate tokens will no longer resolve after the purge.

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?

A single front-loaded sentence that establishes the irreversible, RAM-only nature of the operation before naming the target scope. No filler, though the terseness contributes to the gaps in guidance and post-condition disclosure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter tool with no output schema and rich annotations, the description covers purpose, scope, and the in-memory-only blast radius. The missing pieces are sibling differentiation and the downstream effect on token resolution, which are moderate rather than critical gaps here.

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

Parameters3/5

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

Schema description coverage is 100% and the sessionId description already explains that omitting it or passing an empty string clears all sessions. The description's 'for a specific sessionId or all active sessions' restates that, adding no new semantics such as format, validation, or error behavior for unknown IDs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific destructive verb ('zeroizes') and a precise resource ('volatile in-memory surrogate token mappings'), with the scope spelled out as a single sessionId or all active sessions. However, it never distinguishes itself from the closely-named sibling 'guard_session_reset', leaving the agent to infer the difference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named despite a near-identical sibling ('guard_session_reset'). The clause about omitting sessionId is scope information that duplicates the schema, not guidance on when this tool is the right choice.

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