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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cards.setSuspended

cards_setSuspended

Suspend or unsuspend Anki cards by ID. Idempotent: re-running the same request is safe, and changed=false reports cards already in the requested state.

Instructions

Suspend or restore cards idempotently.

changed=false means already in requested state. Process repeated mutation IDs once and repeat their result.

Anki-Connect method cards.setSuspended. Scope: collection. Effect: write. Completion: completed. Undo: perItem.

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": {
      "ids": "<ids>",
      "suspended": "<suspended>"
    },
    "name": "cards_setSuspended"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesCard IDs (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.
suspendedYestrue to suspend, false to unsuspend.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses idempotency, the meaning of changed=false, duplicate mutation-ID handling, collection scope, completion behavior, per-item undo, and possible errors. These details substantially clarify the operational contract and are consistent with readOnlyHint=false and destructiveHint=false.

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?

The purpose is front-loaded, and the short paragraphs efficiently separate result semantics, operational metadata, and errors. However, the telegram-style metadata and the sentence about repeated mutation IDs are somewhat dense and cryptic.

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 simple three-parameter write operation, the description and schema provide nearly everything needed for correct invocation, including idempotency, undo behavior, and failures. Because there is no output schema, the limited explanation of the result beyond changed=false and the unclear origin of mutation IDs leave minor interpretive gaps.

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 schema already explains ids, suspended, and session thoroughly. The description connects the requested state to no-op behavior but adds little further parameter-specific meaning, making the high-coverage baseline appropriate.

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?

The opening sentence specifies both operations and the resource: suspending or restoring cards. The exact Anki-Connect method name and the suspension-specific behavior clearly distinguish it from siblings such as cards_move and cards_setFlags.

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 description provides clear selection context: use this to change existing cards' suspension state in either direction, with safe repetition. It does not explicitly state prerequisites, when not to use it, or alternatives for other card-state changes.

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