Skip to main content
Glama
Sign In
anki-mcp

anki-mcp

by hbd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_deck

Create a new deck in Anki to organize flashcards, supporting nested deck structures with '::' notation for hierarchical organization.

Instructions

Create a new deck in Anki.

Args: deck_name: Name of the deck to create. Use '::' for nested decks (e.g., 'Parent::Child')

Returns: The deck ID of the created deck

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

Input Schema

NameRequiredDescriptionDefault
deck_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a new deck and returns a deck ID, which covers the basic operation and output. However, it lacks details on permissions, error handling, or side effects (e.g., impact on existing decks).

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?

The description is front-loaded with the core purpose, followed by clear sections for arguments and returns. Each sentence is necessary and informative, with no wasted words, making it efficient and well-structured.

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?

Given the tool's moderate complexity (single parameter, no annotations, but with an output schema), the description is mostly complete. It explains the parameter and return value well, but could benefit from more behavioral context (e.g., error cases). The output schema likely covers return details, reducing the need for extensive output explanation.

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

Parameters5/5

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

The schema description coverage is 0%, so the description must compensate. It fully explains the single parameter 'deck_name', including its purpose, format, and an example ('Parent::Child' for nested decks). This adds significant meaning beyond the bare schema.

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 specific action ('Create a new deck') and resource ('in Anki'), distinguishing it from sibling tools like 'list_decks' or 'get_deck_stats'. It precisely defines the tool's function without ambiguity.

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

Usage Guidelines4/5

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

The description implies usage when a new deck is needed in Anki, but it does not explicitly state when to use this tool versus alternatives like creating nested decks through other means or handling existing decks. It provides context but lacks explicit exclusions or comparisons to siblings.

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