notlai-mcp

by lzientek

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

notlai_delete_note

Delete a note permanently using its unique ID. This action cannot be undone.

Instructions

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

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": {
      "noteId": "<noteId>"
    },
    "name": "notlai_delete_note"
  }
}

Input Schema

Name	Required	Description	Default
`noteId`	Yes	The note ID to delete (ULID format)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0Jul 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Discloses permanent deletion and irreversibility, which is the key behavioral trait. No annotations are provided, so description carries burden; lacks details on permissions, side effects, or error conditions.

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, no filler. Every word earns its place.

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?

Adequately describes the operation and key constraint (irreversible). Missing return value or error handling details, but acceptable for a simple delete with no output schema.

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% with clear parameter description. Tool description adds no new parameter semantics beyond what schema already provides.

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?

Clearly states verb 'delete' and resource 'note', specifies permanence and deletion by ID. Distinguishes from siblings like `bulk_delete_notes` (bulk) and `move_note` (move).

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?

Implies usage for single note deletion by ID and warns of irreversibility, but does not explicitly differentiate from `bulk_delete_notes` or provide when-not-to-use guidance.

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