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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cards.getMany

cards_getMany
Read-only

Retrieve Anki cards by their IDs and return results in the same order as the supplied IDs for consistent batch lookups.

Instructions

Get cards in input order.

Anki-Connect method cards.getMany. Scope: collection. Effect: read. Completion: completed. Undo: none.

Possible errors: collectionUnavailable, 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": {
      "ids": "<ids>"
    },
    "name": "cards_getMany"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesCard IDs (decimal string, e.g. "1700000000001"); results keep input order.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only and non-destructive, but the description adds genuinely new context: scope (collection), completion semantics, 'Undo: none', and an enumerated set of error outcomes. It stops short of saying whether a single missing ID fails the whole call or yields a partial result, which matters given `notFound` is listed.

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 behavior, then structured metadata lines (method, scope, effect, completion, undo, errors) that are easy to scan. 'Effect: read' mildly duplicates readOnlyHint, and the blank-line-separated error line adds a little visual weight, but nothing is padded.

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?

With no output schema, the description never indicates what a returned card looks like or how results behave when some IDs are missing or invalid. The error enumeration and scope line cover the invocation side well, but the return-side gap leaves an agent guessing about partial-failure semantics.

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 both `ids` and `session` are already well documented inside the schema, including the ordering guarantee and the staleSession tradeoff. The description adds nothing about parameter format or constraints beyond that, so the baseline 3 applies.

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 ('Get cards') plus the defining characteristic of this batch variant ('in input order'), which separates it from a single-card getter. It does not explicitly name the sibling it replaces (cards_get / cards_search), so the differentiation is inferred rather than stated.

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 the batch-retrieval framing and the required `ids` array, but there is no explicit 'use this instead of cards_get when you have multiple IDs' instruction. The only real conditional guidance lives in the schema's `session` parameter description, not in the tool description itself.

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