Skip to main content
Glama
Sign In
reMarkable MCP Server

reMarkable MCP Server

by rbonitz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

remarkable_rename

Rename any document or folder on your reMarkable tablet by providing the current name and the new display name.

Instructions

Rename a document or folder on the reMarkable tablet. Changes the display name of a document or folder by updating its metadata. Find the document name with remarkable_browse() first.

Works in cloud and SSH modes (default; --read-only disables). Not available over the USB web interface.

  • document: Current name or path of the document/folder

  • new_name: New display name

  • remarkable_rename("Untitled", "Meeting Notes 2024-01-15")

  • remarkable_rename("/Work/Draft", "Final Report")

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": {
      "document": "<document>",
      "new_name": "<new_name>"
    },
    "name": "remarkable_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYes
new_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already indicate readOnlyHint=false (write operation). The description adds that renaming updates metadata, works in cloud/SSH modes, and is disabled with --read-only. No side effects or permissions are mentioned, but the annotations cover the basic behavioral trait.

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 is well-structured with <usecase>, <instructions>, <parameters>, and <examples> tags. It is slightly verbose but each section adds value. The examples are concise and helpful. Minor redundancy (e.g., 'Change the display name' in both usecase and instructions) could be trimmed.

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?

Given the tool's simplicity (2 string params), the description covers core aspects: purpose, prerequisite, mode restrictions. An output schema exists, so return value details are not needed. Could mention error scenarios or case sensitivity, but overall adequate for this tool.

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

Parameters5/5

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

The schema has 0% description coverage, so the description's <parameters> section fully explains both parameters: 'document' as current name/path and 'new_name' as new display name. Examples further clarify usage. This adds essential meaning beyond the bare schema.

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 the tool renames documents/folders on the reMarkable tablet using <usecase> and mentions updating metadata. It differentiates from siblings like remarkable_browse by suggesting to find the document name first with that tool.

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?

The <instructions> section advises to find the document name with remarkable_browse() first, and specifies compatibility with cloud and SSH modes but not USB web interface. It lacks explicit when-not-to-use or comparisons to alternative rename-related tools like remarkable_move, but provides solid usage context.

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