Skip to main content
Glama

remnote_guide

Get guidance on finding notes, drafting flashcards, and organizing documents in RemNote, including screens and the sign-in link; call this first.

Instructions

How to work in RemNote (find notes, draft flashcards and organize documents in your own RemNote account): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remnote_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in RemNote, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It states that the guide covers RemNote screens and a sign-in link and should be called first, which adds useful context about its informational nature. However, it does not clarify whether the tool is read-only, what form the guidance takes, or whether it has any side effects.

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 two sentences and front-loads the tool's purpose before the key instruction 'Call this first.' It is compact with no obvious waste, though the parenthetical could be tightened.

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

Completeness3/5

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

For a simple onboarding guide with one optional parameter and no output schema, the description covers what the tool is and when to call it. It stops short of explaining what the guide returns or how an agent should use the sign-in link, which leaves a modest gap for an unannotated informational tool.

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 coverage is 100%, and the single optional 'task' parameter is already well described in the schema as 'What you want done in RemNote, in your words.' The description does not add any further meaning or examples for this parameter, so 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 identifies this as a how-to/guide resource for working in RemNote, naming concrete coverage areas (finding notes, drafting flashcards, organizing documents, screens, sign-in link). It is distinct from the sibling action tools (click, open, type, read), though it does not explicitly use a verb like 'returns' or 'explains' to define the tool's output.

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 instruction 'Call this first' gives explicit ordering guidance and implies this is an onboarding step before using the action tools. It does not name alternatives or state when not to use it, but the sequencing context is clear.

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