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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cards.get

cards_get
Read-only

Retrieve a stored Anki card's state by ID without rendering it or predicting answers, enabling direct inspection of card data.

Instructions

Read stored card state without rendering or predicting answers.

Anki-Connect method cards.get. 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": {
      "id": "<id>"
    },
    "name": "cards_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCard ID (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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, but the description goes further by declaring scope (collection), completion semantics (completed), and undo: none, plus an enumerated error set (collectionUnavailable, notFound, staleSession, etc.) an agent can handle programmatically. It stops short of describing what shape the returned "card state" takes, which matters since no output schema exists.

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?

The behavioral core is front-loaded in the first sentence, followed by a compact, consistently formatted metadata block (scope/effect/completion/undo/errors) with no filler. Every line is scannable and nothing needs to be re-read.

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 single-record read with a fully documented two-parameter schema and explicit read-only annotations, the definition covers invocation risk, error handling, and cross-call session semantics well. The one real gap is the absence of any indication of what fields the returned card state contains, which the missing output schema would otherwise have carried.

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 coverage is 100% and the `id` and `session` descriptions in the schema are already rich, including the exact stale-session failure mode. The prose adds no parameter meaning beyond that, so the baseline 3 applies — the schema does all the work here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Read stored card state") and immediately scopes it by exclusion ("without rendering or predicting answers"), which cleanly separates it from cards_render and scheduling_predict in the sibling list. It also names the underlying Anki-Connect method, anchoring the tool to a known API surface.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause "without rendering or predicting answers" tells an agent when this tool is the wrong choice, implicitly routing rendering to cards_render. It does not explicitly name cards_getMany for bulk reads or cards_search for lookup-by-query, so the disambiguation from those siblings is left to inference.

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