Skip to main content
Glama

local-mcp

by com.local-mcp

Delete Note

delete_note
Destructive

Deletes a note from Apple Notes, by ID or exact title. Like deleting it in the app, the note goes to "Recently Deleted" and Apple purges it after 30 days — the user can still recover it there. Requires confirm=true. The result is VERIFIED: the tool re-reads the note after deleting and reports the deletion as unverified if it is still where it was, so a success here means the note is really gone from list_notes/search_notes/read_note. Find note_id with list_notes or search_notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNo
note_idNoThe note's id, as list_notes/search_notes report it.
note_nameNoExact title, when you don't have the id. If several notes share it, the first match is deleted — prefer note_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
deletedNoTrue only when the deletion was VERIFIED by re-reading the note
in_trashNoThe note moved to Recently Deleted (Apple purges it after 30 days) rather than vanishing outright
verifiedNoThe note was re-read after deleting and is no longer where it was
folder_afterNoWhere it ended up (present when it moved instead of vanishing)
next_actionsNo
folder_beforeNoThe folder the note was in before deleting

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses the soft-delete behavior (Recently Deleted, 30-day purge, recoverable), the confirmation requirement, and the post-delete verification step that re-reads the note. This gives the agent a strong model of side effects and success semantics.

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 dense sentences, each adding new information: the core action, the recovery behavior, the verification guarantee, and how to obtain the ID. There is no filler or repetition of the title or annotations.

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?

The description covers the destructive side effect, recovery window, confirmation flag, verification behavior, and lookup method. With an output schema present, the agent has everything needed to invoke delete_note correctly and interpret its result.

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

Parameters5/5

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

The description adds meaningful detail beyond the schema: confirm must be true, note_id is obtainable from list_notes/search_notes, and note_name matches exact titles with first-match behavior and a preference for note_id. It covers both parameters that lack detailed schema descriptions and adds useful context to the one that has them.

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 ('Deletes') and resource ('a note from Apple Notes'), and clarifies the two modes of identification (ID or exact title). This clearly distinguishes delete_note from siblings like update_note, create_note, read_note, and list_notes.

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?

The description gives concrete when-to-use guidance: it requires confirm=true, explains how to find the note_id via list_notes or search_notes, and warns to prefer note_id when titles are ambiguous. It does not explicitly list alternatives or when not to use this tool, but the context is clear enough for correct selection.

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

All local-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation3/5

Many tools are clearly distinct per app (e.g., chrome_*, safari_*, m365_*), but there is notable overlap between generic file tools like `file_list` and `finder_list`, both listing files; `search_contacts` and `list_contacts` serve similar purposes; `report_friction` and `report_problem` both send feedback to the team. The large number of tools with similar purposes in different domains creates moderate ambiguity for an agent.

Naming Consistency4/5

The naming convention is very consistent overall: most tools follow a `{app}_action` or `verb_noun` pattern (e.g., `chrome_click`, `create_calendar_event`, `list_reminders`). There are minor deviations like `lmcp_install_upgrade` (two verbs) and `complete_omnifocus_task` vs. `complete_reminder` (inconsistent verb placement). Still, the pattern is predictable and readable across the full set.

Tool Count2/5

With 225 tools, the surface is extremely large and heavy. While it covers many distinct domains (browsers, mail, calendar, files, notes, reminders, video editing, web automation, etc.), the sheer number makes it hard to navigate and likely includes many rarely-used tools. This is far beyond the well-scoped range of 3-15 tools and feels excessive even for a 'local everything' MCP server.

Completeness3/5

For many app integrations, the tool set provides solid CRUD coverage (e.g., Calendar has create, read, update, delete; Apple Notes has create, read, update, list, search; OmniFocus has create, list, search, complete). However, some areas are incomplete: for example, there is no tool to create a new Mail folder or delete notes. The 'web' tools lack a clear update/delete for saved sessions. The suite is broad but has notable gaps within individual domains.

Resources