Skip to main content
Glama
Sign In
anki-connect-mcp

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

editors.openNote

editors_openNote

Opens the custom note editor for a given note ID, waiting until the editor is ready for viewing or editing.

Instructions

Open the custom note editor and finish once it is ready.

Anki-Connect method editors.openNote. Scope: collection. Effect: gui. Completion: operation. Undo: none.

Long-running operation: by default the server waits for the final result (see waitForCompletion / timeoutSeconds).

Possible errors: collectionUnavailable, editorConflict, internalError, invalidParams, notFound, staleSession.

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": {
      "noteId": "<noteId>"
    },
    "name": "editors_openNote"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYesNote to edit (decimal string, e.g. "1700000000001").
sessionNoOptional. Collection session ID: the `session` field returned by `collection_get`. Usually omit it — the server then uses the session current at the time of the call. Pass it to make the call fail with `staleSession` instead of acting on a different profile/collection than the one your IDs, cursors and tokens came from.
timeoutSecondsNoMCP option (not sent to Anki): how long to wait for completion. A timeout does not cancel the work; the pending record is returned.
waitForCompletionNoMCP option (not sent to Anki): poll operations.get until the operation finishes and return its final record. If false, return the operation handle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses scope (collection), effect class (gui), completion model (operation), and notably "Undo: none" for a GUI-mutating action. It also explains that the call is long-running, that the server blocks by default, that a timeout does not cancel the work, and enumerates the possible error codes including `editorConflict` and `staleSession`. This is exactly the context annotations cannot carry.

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?

Front-loaded with the core action in the first sentence, followed by compact labeled metadata (Scope/Effect/Completion/Undo) and an error list. The format is slightly boilerplate-heavy but no sentence is filler; nothing essential is buried.

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 GUI-opening tool with no output schema, the definition covers what an agent needs to call it correctly: blocking semantics, timeout caveat, session handling, and failure modes. It stops short of describing what the returned operation record contains or what state the editor is left in, which would have made it fully self-sufficient.

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 baseline is 3. The description mentions `waitForCompletion` / `timeoutSeconds` only to restate the waiting behavior already documented in the schema, and adds no syntax or constraints for `noteId` or `session` beyond what the schema provides.

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?

"Open the custom note editor and finish once it is ready" gives a specific verb and resource, and the required `noteId` makes it distinguishable from `editors_openAdd`. However, the description never explicitly contrasts itself with the sibling `editors_openAdd` or `editors_updateDraft`, so differentiation comes mostly from the name and schema.

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 only implied: an agent can infer this is for opening the editor on an existing note rather than creating one. There is no explicit "use this when…" statement, no exclusion of `editors_openAdd`/`editors_updateDraft`, and no stated prerequisite (e.g., does a collection session need to be active first?). The default-wait behavior is explained, which helps invocation but not selection.

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