Skip to main content
Glama

remnote_read

Read the current RemNote page to extract its text, numbered buttons, links, and fields; optionally limit reading to a specific element for focused note review.

Instructions

Read the current RemNote page: its text and numbered buttons, links and fields.

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the shape of the returned content and usefully signals that buttons come back 'numbered' (presumably the handles used by remnote_click). It does not state that the operation is non-mutating, what happens if no page is open, or how the output is formatted or truncated.

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?

A single tight sentence with the resource first and the payload enumerated after the colon, so nothing is wasted. It is arguably too compact for a tool with an unmentioned parameter and no return-format detail.

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?

With no output schema and no annotations, the description must carry the whole contract; describing the returned items is a good start, but it leaves out how the element parameter scopes the read and what the agent receives structurally. Adequate but with clear gaps for a read tool an agent must act on.

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 parameter 'element' is already documented in the schema as 'Read only inside this element.' The description adds no scoping, identifier format, or nesting behavior beyond that, so the baseline of 3 applies.

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?

States a specific verb ('Read') and an unambiguous resource ('the current RemNote page'), then enumerates what it yields: text, numbered buttons, links and fields. That distinguishes it from all listed siblings (click/close/guide/open/status/type), none of which read page content, though the description never explicitly names those alternatives.

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

Usage Guidelines3/5

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

'The current RemNote page' implies a page must already be open, which hints at a dependency on remnote_open, but this is inference rather than stated guidance. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for related needs.

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