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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

deckPresets.get

deckPresets_get
Read-only

Retrieves a deck options preset by ID or name, returning its typed settings for inspection or reuse. Use it to read preset details without changing the Anki collection.

Instructions

Read a typed preset.

Anki-Connect method deckPresets.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": {
      "preset": "<preset>"
    },
    "name": "deckPresets_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYesDeck options preset: exactly one of {"id": "<presetId>"} or {"name": "<preset name>"}.
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.7/5.0
Behavior4/5

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

Beyond the readOnly/non-destructive annotations, the description adds real operational context: collection scope, completion status, that no undo entry is created, and an enumerated error set including notFound and staleSession. That error list is the sort of behavior annotations cannot convey, though return shape remains unspecified.

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 action is front-loaded in one short sentence, followed by scannable metadata fields and an error list. No padding, though the repeated method-name line is largely redundant with the title.

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 two-parameter read tool with full schema coverage and no output schema, the description covers scope, effect, side effects, and failure modes adequately. Only a hint about what a preset record contains is missing, which is minor for a read operation.

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 the `preset` union already documents the exactly-one-of id-or-name rule, so the schema carries the parameter burden. The description only echoes this with "typed preset" and adds nothing about id/name resolution or precedence.

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?

The opening sentence gives a specific verb and resource ("Read a typed preset"), and the method name plus scope line pin it to deck options presets rather than decks or note types. It does not explicitly contrast with the sibling deckPresets_list, though the word "typed" implies a single addressed item rather than enumeration.

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 "Effect: read" against the create/update/delete/assign siblings, but there is no explicit statement of when to prefer this over deckPresets_list or what precondition (e.g. needing full preset details) selects it. The agent must infer the choice from the names alone.

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