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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

profiles.switch

profiles_switch
Destructive

Switch the active Anki profile and wait until the destination collection is ready before continuing.

Instructions

Switch profiles and finish when the destination collection is ready.

Anki-Connect method profiles.switch. Scope: application. Effect: lifecycle. Completion: operation. Undo: none.

Long-running operation: by default the server waits for the final result (see waitForCompletion / timeoutSeconds).

Possible errors: busy, cancelled, internalError, invalidParams, notFound.

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": {
      "name": "<name>"
    },
    "name": "profiles_switch"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the profile to open (see `profiles_list`).
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.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and closed-world scope, and the description usefully reinforces this with "Undo: none" and a lifecycle effect class, plus an enumerated error set (busy, cancelled, notFound, etc.). It stops short of saying what happens to the current collection state or session on switch, which is the one behavior an agent most needs to know for a destructive lifecycle call.

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 core action and completion criterion are front-loaded in one sentence, followed by compact labeled metadata lines. The terse "Scope/Effect/Completion/Undo" fragment style is efficient, though slightly jargon-like, and no sentence is wasted.

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 one-required-parameter lifecycle operation with no output schema, the definition covers completion behavior, timeout semantics, the operations.get polling path, and the failure modes. The remaining gap is the absence of any warning about the state consequences of switching profiles while another operation is in flight.

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% and each parameter is already fully documented, including that waitForCompletion and timeoutSeconds are MCP-only options not sent to Anki. The description only echoes those names and adds no syntax, constraints, or interaction semantics beyond the schema, so the baseline 3 applies.

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 ("Switch profiles") plus a completion condition ("finish when the destination collection is ready"), which distinguishes it from profiles_list and profiles_getActive in the sibling set. An agent can identify the operation without opening the schema.

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 only implied by the verb and by the reference to `profiles_list` in the `name` parameter; there is no explicit statement of when to switch versus inspecting the active profile via profiles_getActive, nor any prerequisite or when-not guidance. The long-running note routes the agent to waitForCompletion/timeoutSeconds, which is useful but parameter-level rather than usage guidance.

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