Skip to main content
Glama

Delete Note

delete_note
DestructiveIdempotent

Use only when the user explicitly asks to delete or discard a specific note. The user can restore it from their dashboard for a short window, but treat it as permanent — confirm which note (by title) if there is any ambiguity. Addressed by the id from list_notes. Fails cleanly if the note is set to read-only for AI assistants.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe note id to delete

Output Schema

NameRequiredDescriptionDefault
idYes
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses the recovery model (restorable from the dashboard for a short window, but treat as permanent) and a failure mode (fails cleanly when the note is read-only for AI assistants). These are exactly the behavioral facts an agent needs before invoking a destructive tool.

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?

Four short sentences, each carrying a distinct decision-relevant fact, with the restrictive usage condition front-loaded ahead of recovery and failure details. No filler or restatement of the tool name.

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 single-parameter destructive tool with an output schema and full annotation coverage, the description covers usage, confirmation, recoverability, and the read-only failure path. Minor gaps remain, such as what happens to attached comments or discussions, but nothing needed to invoke it correctly is missing.

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 single 'id' parameter is already documented as a UUID-formatted note id, so the schema does the heavy lifting. The description adds only the provenance hint that the id comes from list_notes, which is mildly useful but not substantive meaning beyond the schema.

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 and resource ('delete or discard a specific note') and scopes it to an explicit user request, which cleanly separates it from sibling read tools like list_notes or get_note. An agent can tell immediately that this is the destructive removal path for a single note.

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?

It gives a clear use condition ('only when the user explicitly asks to delete or discard') plus an ambiguity-handling rule (confirm by title) and points to list_notes as the source of the id. It stops short of naming an explicit alternative for cases where deletion is not warranted (e.g., update_note or archival), so it is strong but not fully exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.