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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

deckPresets.create

deckPresets_create

Creates a new deck preset, optionally copying settings from an existing preset by ID or name or using Anki defaults.

Instructions

Create a preset by cloning a specified preset or native defaults.

Anki-Connect method deckPresets.create. Scope: collection. Effect: write. Completion: completed. Undo: single.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new preset.
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.
cloneFromNoPreset to copy settings from: exactly one of {"id": "<presetId>"} or {"name": "<preset name>"}. Omit to start from Anki defaults.

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 cover the safety profile (write, non-destructive, non-open-world), and the description adds genuinely new behavior: scope=collection, completion state, single-step undo support, and the enumerable failure modes including collectionUnavailable and editorConflict. It stops short of saying what the call returns or what happens to an existing preset with a conflicting name.

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 purpose sentence followed by compact structured metadata lines (scope, effect, completion, undo, errors) that each carry distinct information. The 'Anki-Connect method deckPresets.create' line is mild redundancy against the tool name but harmless.

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?

Strong for a write tool: annotations plus explicit undo semantics and an error catalogue leave little ambiguity about invocation risk. The remaining gap is the absence of any return-value description (no output schema), so an agent cannot know whether the created preset's ID comes back in the response.

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 (name, session, cloneFrom with its id/name variants) is already documented in the schema, including the 'omit to start from Anki defaults' case. The description's one line about cloning restates rather than extends that meaning, so 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 ('Create a preset') plus the mechanism ('by cloning a specified preset or native defaults'), which is enough to separate it from deckPresets_update, deckPresets_assign, and deckPresets_list without consulting their schemas.

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 'Effect: write' and scope/error metadata imply the creation context, and the omit-cloneFrom behavior is documented, but there is no explicit statement of when to prefer this over deckPresets_update or decks_create, and no prerequisites (e.g., whether the newly created preset must be assigned separately).

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