Skip to main content
Glama
Sign In
@lifeng688/anki-mcp

@lifeng688/anki-mcp

by guanweiqiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_deck

Create a new Anki deck. Supports hierarchical decks using double colons (::) as separators.

Instructions

Create a new Anki deck. Supports hierarchical decks using :: separator.

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

Input Schema

NameRequiredDescriptionDefault
deckNameYesName of the deck to create. Supports hierarchy with ::.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. It mentions creation and hierarchy but does not disclose behavior if deck already exists, error handling, or mutation details. Insufficient for a mutation tool.

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 concise sentences with front-loaded purpose. No wasted words.

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?

Simple tool with one parameter and no output schema; description covers basic purpose and hierarchy but omits return value or error conditions. Adequate but not thorough.

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 coverage is 100% with parameter description already explaining hierarchy. Tool description adds 'new' and 'Anki' but not substantial extra meaning. Baseline 3 is appropriate.

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?

The description clearly states the verb 'create' and resource 'Anki deck', and distinguishes from sibling tools like list_decks or add_note. It also mentions hierarchical support via '::'.

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?

No explicit guidance on when to use this tool versus other tools. No mention of prerequisites or context. The description is self-evident for a creation tool but lacks explicit alternatives or conditions.

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