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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser.open

browser_open

Open Anki's card browser with an optional search query and column sort, then wait until the search completes so you can inspect filtered cards immediately.

Instructions

Open the browser and finish after the requested search/sort completes.

Omitted query preserves existing browser search. Explicit direction is applied regardless of previous/default column order.

Anki-Connect method browser.open. 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, internalError, invalidParams, invalidSearch, invalidState, staleSession.

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": "browser_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOptional browser-column sort, e.g. {"column": "noteFld", "direction": "ascending"} (`column` is an Anki browser column key such as noteFld, cardDue). Default: ascending ID order.
queryNoSearch to show in the browser; omit to keep the browser's default.
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.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: scope (collection), effect (gui), completion model (operation), undo: none, a default wait-for-completion behavior, and an enumerated error list. It does not contradict the annotations, and the GUI side effect is consistent with readOnlyHint=false while remaining non-destructive. Minor gap: it doesn't say what happens to an already-open browser window.

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 purpose, then the behavioral facts in a compact labeled form (Scope/Effect/Completion/Undo) and a short caveat about long-running behavior. The staccato fragments are efficient, though the error-code list adds bulk of marginal value for an agent.

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?

No output schema exists, yet the description explains that the final operation record is returned by default and an operation handle is returned otherwise, and it names failure modes. Combined with full schema coverage, an agent has nearly everything needed; only the concrete result payload shape is left implicit.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: query omission preserves the *existing* search (richer than the schema's 'default'), and the explicit-direction rule clarifies how sort interacts with prior column ordering. The waiting/timeout behavior is summarized and deferred to the schema fields.

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 and resource ('Open the browser') plus what it does with query/sort, wrapped around the Anki-Connect method `browser.open`. It is clearly distinct from sibling GUI tools like browser_select or browser_getSelection, though it never names them explicitly.

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?

Gives useful conditional rules ('Omitted query preserves existing browser search', 'Explicit direction is applied regardless of previous/default column order') and flags the long-running/waiting behavior, but offers no when-to-use-vs-alternative guidance or exclusions relative to siblings such as browser_select or application_navigate.

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