Skip to main content
Glama
Jackxiaozhiren

datasentry

by Jackxiaozhiren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pii_delete_session

Destructive

Deletes a PII encryption session, permanently removing its encrypted mapping without needing the encryption key. Requires confirmation and returns deleted=true, or ok:false if no session exists.

Instructions

Delete a PII encryption session (Step 100, ADR-100). Removing the encrypted mapping is not reversible and does not require the encryption key. Returns deleted=true or ok:false when the session does not exist.

Input Schema

NameRequiredDescriptionDefault
confirmYesmandatory acknowledgement that this call mutates state; the tool writes nothing unless it is true (D5-08, D5-12)
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "mandatory acknowledgement that this call mutates state; the tool writes nothing unless it is true (D5-08, D5-12)",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "session_id"
-]New value: +[
+  "session_id",
+  "confirm"
+]
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real context: the removal is irreversible, it does not require the encryption key, and it reports deleted=true or ok:false when the session is absent. That return-value disclosure is especially valuable since there is no output schema.

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?

Three tightly written sentences that are front-loaded with the action and immediately followed by the irreversibility caveat and return contract. The '(Step 100, ADR-100)' reference is internal jargon of marginal value but costs little.

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 two-parameter destructive tool with no output schema, the description covers irreversibility, key independence, and the return shape. It stops short of naming the confirm prerequisite explicitly and does not address permissions or effects on related sessions.

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

Parameters2/5

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

Schema coverage is only 50%: confirm is documented in the schema, but session_id has no description anywhere. The description mentions no parameters at all, so it fails to compensate for the undocumented session_id or explain what a session ID refers to.

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?

States a specific verb and resource ('Delete a PII encryption session') and grounds it in an internal reference (Step 100, ADR-100). It does not, however, differentiate itself from the very similar sibling pii_purge_sessions, leaving the agent to infer which delete-like tool applies.

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?

The description explains what the tool does and warns that the operation is irreversible, but never says when to choose it over pii_purge_sessions, pii_sessions, or pii_restore. There are no explicit preconditions beyond the schema-level confirm gate, and no alternatives are named.

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