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

anki-workflow-mcp

by Gugart43
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Deck Hierarchy Sync

deck_hierarchy_sync

Synchronize Anki deck hierarchy from the live collection.anki2 SQLite database while handling running locks and merging manually added subdecks.

Instructions

Synchronize deck hierarchy from the live Anki SQLite database collection.anki2. Safely handles running Anki locks and merges with any manually added subdecks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deck_hierarchy_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
root_deckNo02_MEDICINA_AnkiMBR
anki_collection_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and usefully discloses that it safely handles running Anki locks and merges manually added subdecks. However, it omits whether the operation is destructive, what permissions are required, whether changes are reversible, and how conflicts are resolved.

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?

Two front-loaded sentences with no filler. The purpose and two key behavioral traits are conveyed efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the lock/merge behavior is a helpful addition. Still, for a synchronization tool with two undocumented parameters and no annotations, the description is incomplete regarding parameter meaning and usage guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters. The description references collection.anki2, which loosely relates to anki_collection_path, but it does not explain the root_deck parameter, its default, the path format, or any parameter behavior.

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?

States a specific verb and resource: 'Synchronize deck hierarchy' from 'live Anki SQLite database collection.anki2'. It is clear what the tool does, though it does not explicitly differentiate itself from the deck_hierarchy_add/get/search siblings.

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

Usage Guidelines2/5

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

Gives no explicit when-to-use or when-not-to-use guidance and does not name alternatives. The source context implies a synchronization scenario, but an agent must infer when this tool should be chosen over the sibling deck hierarchy tools.

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