Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

delete_note

DestructiveIdempotent

Permanently delete a note. Use fetch_notes first to get the note_token. WARNING: This action cannot be undone.

delete_note

When to use

Permanently delete a note. Use fetch_notes first to get the note_token. WARNING: This action cannot be undone.

Parameters to validate before calling

  • note_token (string, required) — The note token to delete (UUID format)

Notes

  • DESTRUCTIVE — IRREVERSIBLE. Always confirm with the user before calling. Explain what will be lost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYesMust be true. Set it ONLY after the user explicitly confirmed THIS deletion in this conversation, having been told what is lost: the note and its encrypted content. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema.
note_tokenYesThe note token to delete (UUID format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true. Set it ONLY after the user explicitly confirmed THIS deletion in this conversation, having been told what is lost: the note and its encrypted content. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "note_token"
-]New value: +[
+  "note_token",
+  "confirm"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

The description prominently warns that the action cannot be undone and instructs to always confirm with the user, which goes beyond the annotations (destructiveHint). It also explains what will be lost, enhancing transparency.

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 concise, using a clear format with sections. It contains no unnecessary words and conveys the essential information quickly.

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 simple two-parameter tool, the description covers the purpose, prerequisite, and safety warning. It lacks details about the response or edge cases, but those are not essential for basic usage.

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?

The schema already provides detailed descriptions for both parameters, especially the confirm parameter. The description text adds only a hint about fetching the token, so the added semantic value is minimal.

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 clearly states the action ('permanently delete a note') and the resource. It is specific enough to distinguish from other delete tools based on the resource type.

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

Usage Guidelines3/5

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

It provides a prerequisite ('Use fetch_notes first to get the note_token') which helps with invocation. However, it does not explicitly compare to alternative tools like update_note or delete_sweepstakes, so the guidance is limited.

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

All Sweeppea MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources