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

anki-workflow-mcp

by Gugart43
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Deck Hierarchy Add

deck_hierarchy_add

Adds a new subdeck to the Anki deck hierarchy, automatically creating any missing parent levels and saving the update immediately.

Instructions

Add a new subdeck to the 02_MEDICINA_AnkiMBR hierarchy and persist the update immediately. subdeck_path: the full or relative subdeck path to add (e.g. '02_MEDICINA_AnkiMBR::Ciclo Clínico::Oftalmologia::Catarata'). Automatically creates all missing parent levels in the hierarchy.

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

Input Schema

NameRequiredDescriptionDefault
root_deckNo02_MEDICINA_AnkiMBR
subdeck_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.4/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 burden. It usefully discloses two behaviors beyond the schema: the change is persisted immediately (a mutation) and all missing parent levels are auto-created. It is silent on what happens if the subdeck already exists (idempotency), whether anything is overwritten, and what failures look like.

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?

Three compact sentences, front-loaded with the action and its persistence semantics, then the key parameter with a concrete example. Nothing extraneous, though the example path is long relative to the information it adds.

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?

For a two-parameter mutation tool with an output schema (so return values need no explanation), the definition is close to sufficient. The remaining gaps are the undocumented root_deck parameter and the absence of any statement about duplicate subdecks or permission requirements.

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 0%, so the description must compensate. It does a good job on subdeck_path, explaining that full or relative paths are accepted and giving a worked example, but root_deck is never mentioned in the description and has no schema documentation, leaving one of two parameters undocumented.

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 description names a specific verb and resource ("Add a new subdeck") and pins it to a concrete hierarchy (02_MEDICINA_AnkiMBR), so an agent can distinguish it from read-oriented siblings like deck_hierarchy_get or deck_hierarchy_search. It does not explicitly contrast itself with those siblings, which keeps it short of a 5.

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: the tool creates decks, so it is presumably used when a deck must exist before cards are added. There is no statement of when to use this versus deck_hierarchy_sync or batch_auto_fix, and no prerequisites or exclusions are given.

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