Skip to main content
Glama

remnote_click

Click a numbered element on the current RemNote page to select or open it using the element number from the last read.

Instructions

Click a numbered element on the current RemNote page.

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": {
      "element": "<element>"
    },
    "name": "remnote_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates that a UI interaction occurs but does not explain possible navigation or page-state changes, stale or invalid element behavior, or what happens after a successful click.

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 single sentence is front-loaded and efficiently identifies the action, target, and page scope without filler. Its brevity is appropriate for a simple tool, with any resulting information gaps assessed under the other dimensions.

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 one-parameter UI action, the description and schema together provide minimally sufficient invocation context. With no annotations or output schema, the lack of an explicit read-first workflow and information about stale numbering, effects, or errors leaves noticeable completeness gaps.

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%, and the schema already explains that element is the element number from the last read, with a minimum value of 1. The description's reference to a numbered element reinforces that meaning but adds little beyond the structured field, making the baseline score appropriate.

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 uses a specific verb and target: clicking a numbered element on the current RemNote page. It clearly conveys the basic operation, though it does not explicitly differentiate the tool from siblings such as remnote_read or remnote_type.

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 references to a numbered element and the current page imply an element-selection workflow, while the schema clarifies that the number comes from the last read. However, the description does not explicitly explain when to use the tool, when to refresh element numbers, or when another action would be more appropriate.

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