Skip to main content
Glama
Sign In
RemNote MCP Server

RemNote MCP Server

by robert7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remnote_search

Search your RemNote knowledge base for notes matching specific queries, with options to limit results and include child content.

Instructions

Search the RemNote knowledge base for notes matching a query

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": {
      "query": "<query>"
    },
    "name": "remnote_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query text
limitNoMaximum results (1-100, default: 20)
includeContentNoInclude child content (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the basic function but lacks critical details: no mention of search algorithm (full-text, fuzzy, etc.), performance characteristics, rate limits, authentication requirements, or what happens with empty/no results. For a search tool with zero annotation coverage, this is inadequate.

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

Conciseness5/5

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

The description is a single, clear sentence with zero waste. It's appropriately sized for a search tool and front-loads the essential information without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the search returns (note metadata, full content, relevance scores), how results are ordered, or any limitations. The agent would need to guess about the output format and search behavior.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Search') and resource ('RemNote knowledge base for notes'), making the purpose immediately understandable. However, it doesn't differentiate from potential sibling search tools (none are listed as siblings, but this could be relevant if there were multiple search variants).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'remnote_read_note' or 'remnote_update_note'. It doesn't mention prerequisites, limitations, or typical use cases for searching versus direct note access.

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