Skip to main content
Glama
Sign In
AI Notes MCP Server

AI Notes MCP Server

by ibrahimbelkahla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete note

delete_note
Destructive

Permanently delete a saved note by ID after asking the user to confirm, preventing accidental removal and keeping notes current.

Instructions

Permanently delete a note. Ask the user for confirmation before calling this.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds two things beyond that: the deletion is permanent (irreversible, no undo/trash) and it requires a user confirmation round-trip before invocation. It says nothing about return values, which is acceptable with no output schema but is a minor gap.

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 short sentences, zero waste, with the operation and its permanence front-loaded and the confirmation requirement second. Nothing could be removed without losing information.

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?

For a single-parameter destructive tool with no output schema, the definition covers operation, irreversibility, and the required confirmation step, while annotations carry the safety hint. Nothing an agent needs 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 coverage is 100% and the single `id` parameter is documented in the schema, so baseline 3 applies. The description adds no format or sourcing detail (e.g., where to obtain the note id) beyond what the schema already states.

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" gives a specific verb and resource, and the permanence qualifier distinguishes it from a soft-delete or archive. It doesn't explicitly name sibling tools, but delete vs. get/list/update/add/search is self-evident from the name.

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 supplies a concrete precondition — obtain user confirmation before calling — which is exactly the guidance an agent needs for a destructive action. There are no explicit when-not conditions or named alternatives, but none are needed given the sibling set is clearly disjoint.

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