Skip to main content
Glama
Sign In
notes-mcp

notes-mcp

by gabed5303-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_note

Destructive

Permanently delete a note by its ID. Provides confirmation with the deleted note's title.

Instructions

Permanently delete a note by ID. This cannot be undone.

Returns a confirmation with the deleted note's title.

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_idYesID of the note to delete.

Output Schema

NameRequiredDescriptionDefault
idYesID of the deleted note.
titleYesTitle of the deleted note.
deletedYesTrue if the note was removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide destructiveHint=true and readOnlyHint=false. The description adds 'This cannot be undone' and 'Returns a confirmation with the deleted note's title', providing behavioral context beyond annotations.

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 consists of two short, front-loaded sentences. The first states the primary action, the second adds critical side effect and return info. No unnecessary words.

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

Completeness5/5

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

Given the tool's simplicity (one required parameter), the presence of annotations, and the mention of return confirmation, the description fully covers necessary context for an agent to use it correctly.

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% with the parameter 'note_id' described as 'ID of the note to delete.' The description merely says 'by ID', adding no additional semantics 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 'Permanently delete a note by ID', clearly indicating the verb (delete), resource (note), and method (by ID). It distinguishes from sibling tools like add, get, list, search, and update.

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 description implies usage for deletion but does not explicitly state when to use this tool vs alternatives, nor when not to use it. It mentions irreversibility but lacks direct comparison to siblings.

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