Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

delete_note

Destructive

Permanently deletes a note and removes links to it from other notes. Requires confirm=true, cannot be undone; use move_note instead to relocate.

Instructions

Delete one note for good; the links to it are removed from the other notes.

Call it only when the user asked to delete that note; to put it elsewhere, use move_note. Cannot be undone. Without confirm=true it refuses and changes nothing. Returns the note deleted; an unknown path returns an error.

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

Input Schema

NameRequiredDescriptionDefault
pathYesThe note's path, e.g. finance/pricing.md
confirmNotrue when the user asked for it: it cannot be undone

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real context beyond them: cross-note link removal, irreversibility, and the confirm gate that refuses and changes nothing without confirm=true. It also notes the error behavior for unknown paths, though it does not cover permissions or concurrency concerns.

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?

Front-loaded with the action and its destructive side effect, then usage routing, then the safety gate. Every sentence carries distinct information with no filler.

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 destructive two-parameter tool with an output schema, the description covers the action, side effects, irreversibility, the confirmation requirement, and error behavior. An agent has everything needed to call it safely and correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds behavioral meaning the schema does not: confirm=true is a hard gate whose absence causes a no-op refusal, and an unknown path yields an error. That is genuine semantic value beyond the field descriptions.

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?

States a specific verb and resource ('Delete one note') and immediately adds the scope-defining side effect that links to it are removed from other notes. It also names the sibling it is not (move_note), so an agent can distinguish it without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use condition ('only when the user asked to delete that note') and an explicit alternative with its selecting condition ('to put it elsewhere, use move_note'). Nothing about routing is left to inference.

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