Skip to main content
Glama

remnote_status

Check that your Cotlet.dev account, credits, and RemNote connection are ready before using the server, so you can verify setup and avoid failures during note, flashcard, or document tasks.

Instructions

Check that your Cotlet.dev account and RemNote are ready: account, credits and RemNote connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description carries the full behavioral burden. It does disclose the three things inspected (account, credits, RemNote connection) and hints at an auth/account prerequisite, but it does not say whether the call is read-only, whether it consumes credits, or what a failed check looks like (and there is no output schema to compensate).

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 front-loaded sentence with no filler, and the colon-separated list of checked items is easy to scan. It could be nudged higher only by adding one short clause on what the result indicates, without bloating.

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?

For a simple zero-parameter status tool with no output schema, naming the three checked facets is close to sufficient. The remaining gap is what the response conveys on success versus failure and whether any account/credit precondition must be met first.

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?

The tool takes zero parameters, so per the baseline there is nothing the description needed to disambiguate. The sentence correctly makes no parameter claims and adds no misleading argument information.

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 states a specific verb ('Check') and enumerates what readiness covers: account, credits, and RemNote connection. That clearly distinguishes it from the sibling tools (click, close, open, read, type), which are UI actions, though it does not explicitly contrast itself with any of them.

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?

Usage is implied by 'Check that ... are ready' — an agent can infer this is a pre-flight/diagnostic call. However, there is no explicit statement of when to call it versus when not to, nor any sequencing advice such as running it before other operations when errors occur.

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