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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notes.findEmpty

notes_findEmpty
Read-only

Find empty notes or cards to clean up by criterion—all fields empty, no cards, or all questions empty—optionally filtered by an Anki search query. Returns matching IDs only; no deletion.

Instructions

Find cleanup candidates by an explicit criterion.

No deletion. allFieldsEmpty uses native HTML-aware emptiness; allQuestionsEmpty uses native empty-card generation. Return all matching IDs through normal cursor pagination.

Anki-Connect method notes.findEmpty. Scope: collection. Effect: read. Completion: completed. Undo: none.

Possible errors: collectionUnavailable, internalError, invalidParams, invalidSearch, 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": {
      "criterion": "<criterion>"
    },
    "name": "notes_findEmpty"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1–1000 (default 100).
queryNoOptional Anki search query restricting the candidates. Default: whole collection.
cursorNoContinuation token: `nextCursor` from the previous page of the same call. Omit for the first page. Repeat the same query, sort and limit; each cursor is single-use and expires after 10 minutes. `nextCursor: null` means there are no more pages.
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.
criterionYesWhat counts as empty: `allFieldsEmpty`, `noCards` or `allQuestionsEmpty`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description isn't needed for safety basics. It still adds real value beyond them: collection scope, the fact that all matching IDs come back through normal cursor pagination, no undo, and an enumerated error list (collectionUnavailable, invalidSearch, staleSession) that tells the agent what failure modes to handle.

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?

Front-loaded with the purpose sentence, followed by the criterion-distinguishing detail, then a compact metadata line (method, scope, effect, completion, undo) and an error list. Every line carries information; nothing is repeated padding.

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?

With no output schema, the description correctly covers the return contract (all matching IDs, cursor pagination, nextCursor null = done) and error surface. For a 5-parameter read tool with full schema coverage this is nearly complete; only the noCards criterion and any performance/emptiness caveats are missing.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the enum labels alone don't convey: allFieldsEmpty uses native HTML-aware emptiness and allQuestionsEmpty uses native empty-card generation. That clarifies which criterion actually matches what the agent is looking for. The noCards option is left unexplained.

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+resource ("Find cleanup candidates") and names the explicit criterion that drives the search, which lets an agent distinguish it from notes_search and notes_delete. It never explicitly contrasts itself with those siblings, so it stops short of a 5.

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 phrase "cleanup candidates" plus "No deletion" implies this is a read-only discovery step preceding a delete/update call, which is useful implied guidance. But there is no explicit "use this instead of notes_search when..." routing and no stated prerequisites, so the agent must infer the workflow.

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