Skip to main content
Glama
rbonitz

reMarkable MCP Server

by rbonitz

remarkable_read

Read-onlyIdempotent

Read and extract text from reMarkable documents with pagination, search via grep, and OCR for handwritten annotations.

Instructions

Read and extract text content from a reMarkable document. Extracts content from a document with pagination to preserve context window.

Content types:

  • "text" (default): Full extracted text (PDF/EPUB content + annotations)

  • "raw": Original PDF/EPUB text only (no annotations). Works in every transport, as long as the source file is present (very large PDFs/EPUBs may not be synced to the cloud).

  • "annotations": Only annotations, highlights, and handwritten notes

Use pagination to read large documents without overwhelming context:

  • Start with page=1 (default)

  • Check "more" field - if true, there's more content

  • Use "next_page" value to get the next page

Use grep to search for specific content on the current page.

When REMARKABLE_OCR_BACKEND=sampling is set and the client supports sampling, OCR will use the client's LLM for handwriting recognition (no API keys needed).

  • document: Document name or path (use remarkable_browse to find documents)

  • content_type: "text" (full), "raw" (PDF/EPUB only), "annotations" (notes only)

  • page: Page number (default: 1). For notebooks, this is the notebook page.

  • grep: Optional regex pattern to filter content (searches current page)

  • include_ocr: Enable handwriting OCR for annotations (default: False)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentYes
content_typeNotext
pageNo
grepNo
include_ocrNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already mark the tool as readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable context: pagination with 'more' and 'next_page' fields, OCR behavior based on environment variable, and content type behavior like 'raw' working without annotations. No contradiction with 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?

Description is well-structured with usecase, instructions, parameters, and examples. Each section is useful, though slightly lengthy. It is front-loaded with the usecase and instructions.

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 tool's complexity (5 parameters, output schema exists), the description covers all aspects: purpose, pagination, content types, OCR, grep filtering, and references sibling tool for document discovery. It is complete without needing to explain return values due to output schema.

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?

Schema description coverage is 0%, but the description provides a dedicated <parameters> section explaining each parameter: 'document' as name/path (use browse), 'content_type' with enum explained, 'page' as page number, 'grep' as optional regex, 'include_ocr' default false. This fully compensates for the schema's lack of 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?

Description starts with '<usecase>Read and extract text content from a reMarkable document.</usecase>', providing a specific verb and resource. It clearly distinguishes from sibling tools like remarkable_search (searching) and remarkable_image (images).

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?

Instructions include pagination and content type usage, and mention using remarkable_browse to find documents. However, it does not explicitly state when not to use this tool or compare it to alternatives like remarkable_search.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rbonitz/remarkable-mcp-http-'

If you have feedback or need assistance with the MCP directory API, please join our Discord server