Skip to main content
Glama

delete_note

Delete wiki notes safely by requiring confirmation, creating an automatic backup first, and reporting broken inbound links or a dry-run preview before removal.

Instructions

wiki 노트 삭제 — confirm=True 필수 (파괴적 연산). 자동 백업 후 삭제.

안전장치: - confirm=True 반드시 필요 (실수로 인한 삭제 방지) - 삭제 전 자동 백업 (.bak.) - 삭제 후 inbound link가 broken 될 노트 목록 반환 - dry_run=True 시 삭제 미리보기 (inbound 영향 포함)

Args: id: 삭제할 노트 ID confirm: True MUST — 확인 없는 삭제 거부. 기본 False. dry_run: True 시 미리보기만 반환, 파일 미삭제. 기본 False.

Returns: JSON — status (ok/error/preview), backup, inbound_links_broken, message

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
idYes
confirmNo
dry_runNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the operation is destructive, that a backup file (<name>.bak.<timestamp>) is created automatically, that a confirm flag is required, and that broken inbound links are reported. It omits permissions/authorization requirements and whether the backup can be restored, so it is not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is organized into header, safety bullets, and Args/Returns sections, with the destructive nature and confirm requirement front-loaded. The confirm=True requirement is restated three times across the header, bullets, and Args, which is mild redundancy.

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 three-parameter tool with no annotations, the description covers the safety model, backup behavior, preview mode, and the information returned. An output schema exists, so the Returns section is a harmless redundancy rather than a gap.

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 description coverage is 0%, so the description must compensate, and it does: all three parameters (id, confirm, dry_run) are documented with meaning, defaults, and behavioral effect. The value of confirm is emphasized more than strictly needed, but no parameter is left unexplained.

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 opening line gives a specific verb and resource ('wiki 노트 삭제') and immediately distinguishes the operation as destructive with a mandatory confirm flag. An agent can identify this as the deletion tool among siblings like update_note or create_note without opening the schema.

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 clearly states that confirm=True is mandatory and that dry_run=True produces a preview including inbound-link impact, which effectively tells the agent when to use each mode. It does not compare against alternatives such as archiving or updating a note instead, but the destructive-operation context supplies sufficient usage framing.

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