Skip to main content
Glama

Delete note

delete_note
Destructive

Permanently delete a note or bookmark from your knowledge base after confirming the action with the user.

Instructions

Permanently delete a note or bookmark. Confirm with the user first.

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": {
      "note_id": "<note_id>"
    },
    "name": "delete_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds the useful nuance of permanence and a human-confirmation step. It does not disclose side effects such as whether attached bookmarks or tags are removed, or behavior when the note_id doesn't exist.

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?

Two sentences, front-loaded with the action and its irreversible nature, then the safety instruction. No redundant wording.

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

Completeness3/5

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

With an output schema present, return values need not be explained, and the annotations carry the safety profile. However, for a destructive tool, the definition should say more about cascade effects and identifying the target note; those gaps keep it at a minimum-viable level.

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 description coverage is 0% – the only parameter is documented merely as an integer with a minimum. The description does not explain what note_id refers to or where to obtain it (list_notes, get_note, search_notes), so it fails to compensate for the schema gap.

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?

"Permanently delete a note or bookmark" states a specific verb and resource, clearly distinguishing this removal tool from the update/add siblings. It stops short of naming an alternative (e.g., update_note) for the soft-change case, so it lands just below a 5.

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?

The instruction "Confirm with the user first" gives one concrete prerequisite for invocation. There is no guidance on when not to use it, nor a named alternative for reversible edits, leaving the when-to-use reasoning implied.

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