io.github.praveensehgal/remarkable

remarkable_search

Read-onlyIdempotent

Search across multiple reMarkable documents to find matching content. Filter by tags or use grep to narrow results, with optional OCR for handwritten notes.

Instructions

Search across multiple documents and return matching content. Searches document names for the query, then optionally searches content with grep. Can filter by tags to narrow results. Returns summaries from multiple documents in a single call.

This is efficient for finding information across your library without making many individual tool calls.

Limits:

Max 5 documents per search (to keep response size manageable)
Returns first page (~8000 chars) of each matching document
Use grep to filter to relevant sections
query: Search term for document names
grep: Optional pattern to search within document content
limit: Max documents to return (default: 5, max: 5)
include_ocr: Enable OCR for handwritten content (default: False)
tags: List of tags to filter documents (optional, case-insensitive)
remarkable_search("meeting") # Find docs with "meeting" in name
remarkable_search("journal", grep="project") # Find "project" in journals
remarkable_search("notes", include_ocr=True) # Search with OCR enabled
remarkable_search("project", tags=["work"]) # Find work-tagged projects

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`grep`	No
`limit`	No
`include_ocr`	No
`tags`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Description adds behavioral context beyond annotations: searches document names, optionally content with grep, returns summaries, max 5 docs, first page ~8000 chars. Annotations (readOnlyHint, idempotentHint) are consistent. No contradictions.

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 structured with XML tags (usecase, instructions, parameters, examples) that improve readability. Content is front-loaded with purpose. Each section adds value; examples are helpful. Could be slightly shorter but not redundant.

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 5 parameters, output schema exists, and sibling tools, the description covers purpose, parameters, limits, examples, and usage context. It explains output returns summaries from multiple documents. Adequate for an agent to invoke 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?

With 0% schema description coverage, the <parameters> section provides essential meaning: describes each parameter's purpose and default behavior (e.g., 'optional pattern to search within document content' for grep, 'Enable OCR for handwritten content' for include_ocr). Adds value beyond schema titles.

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 searches across multiple documents and returns matching content, with specific verb 'Search' and resource 'Documents'. Examples further clarify usage. Distinguishes from siblings like remarkable_read (single document) and remarkable_browse (folder listing).

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 description includes explicit usage guidelines: efficient for cross-document search, limits (max 5 docs, first page ~8000 chars), and filtering options. It doesn't explicitly state when not to use, but the context is clear from instructions and sibling tools.

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

Deploy Server