Skip to main content
Glama

anki_create_deck

Create a new Anki deck programmatically using the Model Context Protocol. Specify the deck name to manage flashcards and organize study materials efficiently.

Instructions

Create a new Anki deck

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deckNameYesThe name of the deck to create

Implementation Reference

  • The execution handler for the 'create_deck' MCP tool. It retrieves the deckName argument, validates it, calls the YankiConnect client's deck.createDeck method, and returns a success message.
    case "create_deck": {
      const client = getClient();
      const deckName = String(toolArgs.deckName);
      if (!deckName) {
        throw new Error(
          "deckName parameter is required for create_deck tool."
        );
      }
      await client.deck.createDeck({ deck: deckName });
      return {
        content: [
          { type: "text", text: `Successfully created deck: ${deckName}` },
        ],
      };
    }
  • The tool schema definition for 'create_deck', including name, description, and inputSchema requiring a 'deckName' string.
      name: "create_deck",
      description: "Create a new Anki deck.",
      inputSchema: {
        type: "object",
        properties: {
          deckName: {
            type: "string",
            description: "The name of the deck to create.",
          },
        },
        required: ["deckName"],
      },
    },
  • Registration of the tool list handler, which includes the 'create_deck' tool from getToolDefinitions() in the response to ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      console.error(
        "[MCP Anki Client - tool-manager.ts] Received ListToolsRequest from client."
      );
      const tools = [...getToolDefinitions(), getDeckModelInfoToolDefinition];
      return { tools: tools };
    });
Behavior2/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 'Create a new Anki deck', implying a write operation, but lacks details on permissions, error handling, or what happens if the deck already exists. This is a significant gap for a mutation tool without annotations.

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 a single, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core purpose without unnecessary elaboration.

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

Completeness2/5

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

Given that this is a mutation tool with no annotations and no output schema, the description is incomplete. It fails to address behavioral aspects like side effects, return values, or error conditions, which are crucial for an agent to use the tool effectively.

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?

The schema description coverage is 100%, with the single parameter 'deckName' fully documented in the schema. The description does not add any additional meaning beyond what the schema provides, such as format constraints or examples, so it meets the baseline for high schema coverage.

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 clearly states the action ('Create') and resource ('new Anki deck'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'anki_add_note' or 'anki_add_notes', which are about adding notes rather than creating decks, so it misses explicit sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. There are no mentions of prerequisites, context, or exclusions, leaving the agent to infer usage based on the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nietus/anki-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server