io.github.praveensehgal/remarkable

remarkable_delete

Destructive

Permanently remove documents or folders from your reMarkable tablet. Deletes with full path, including all contents for folders; use browse to verify path first.

Instructions

Delete a document or folder from your reMarkable tablet. Permanently deletes the item at the given path. This cannot be undone.

For folders, all contents are deleted recursively. Use remarkable_browse to verify the path before deleting.

path: Exact path to the document or folder to delete
remarkable_delete("/01 Work/Old Project")
remarkable_delete("/05 Personal/Reading/finished-book.pdf")

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": "remarkable_delete"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate destructiveHint=true. The description adds that deletion is permanent, impossible to undo, and for folders all contents are deleted recursively. This provides valuable behavioral context beyond the annotations.

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 description uses structured XML tags to separate sections, making it easy to parse. It is concise with no superfluous sentences, though the tag format could be streamlined. Each section serves a purpose.

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?

Given the simple destructive nature with one parameter and the presence of an output schema, the description covers all necessary aspects: purpose, permanence, recursion, verification suggestion, and examples. It is fully sufficient for the agent to use the tool 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 has one parameter 'path' with no description (0% coverage). The description explains it as 'Exact path to the document or folder to delete', adding meaning beyond the schema. Examples further clarify format. While not extremely detailed, it's adequate for a single string parameter.

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 clearly states it deletes documents or folders from the reMarkable tablet, which is a specific verb+resource combination. It distinguishes itself from sibling tools like remarkable_browse (browse) and remarkable_move (move).

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?

The instructions explicitly warn that deletion is permanent and cannot be undone, and suggest using remarkable_browse to verify the path before deleting, providing clear when-to-use guidance and an alternative.

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

Deploy Server