Skip to main content
Glama

deck_changeDeck

Move Anki flashcards to a different deck, automatically creating the target deck if it doesn't exist. Organize your study materials by transferring cards between decks.

Instructions

Moves cards with the given IDs to a different deck, creating the deck if it doesn't exist yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYesA list of card IDs to move.
deckYesThe target deck name.

Implementation Reference

  • Full tool handler implementation for changeDeck (prefixed to deck_changeDeck), including decorator, parameters (schema), and logic calling AnkiConnect API.
    @deck_mcp.tool(
        name="changeDeck",
        description="Moves cards with the given IDs to a different deck, creating the deck if it doesn't exist yet.",
    )
    async def change_deck_tool(
        cards: Annotated[List[int], Field(description="A list of card IDs to move.")],
        deck: Annotated[str, Field(description="The target deck name.")],
    ) -> None:
        return await anki_call("changeDeck", cards=cards, deck=deck)
  • Registers all deck_mcp tools into the main anki_mcp server with the 'deck_' prefix, enabling the 'deck_changeDeck' tool.
    await anki_mcp.import_server("deck", deck_mcp)
  • Creates the sub-MCP instance (deck_mcp) where deck tools like changeDeck are registered.
    deck_mcp = FastMCP(name="AnkiDeckService")
Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses that the tool can create decks if they don't exist, which is valuable behavioral context. However, it doesn't mention permissions needed, whether the operation is reversible, what happens if card IDs are invalid, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

Single sentence that efficiently conveys the core functionality with zero waste. Front-loaded with the primary action ('Moves cards'), followed by key behavioral detail ('creating the deck if it doesn't exist yet'). Every word earns its place.

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?

Given 2 parameters with full schema coverage and no output schema, the description adequately explains what the tool does. However, as a mutation tool with no annotations, it should ideally mention more about behavioral aspects like error conditions or side effects. The deck creation detail helps, but doesn't fully compensate for the lack of structured safety/behavioral information.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents both parameters well. The description adds context about deck creation as a side effect of the 'deck' parameter, which provides additional semantic meaning beyond the schema's technical documentation. With 2 parameters and high schema coverage, this earns above baseline.

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 ('Moves cards'), identifies the resource ('cards with the given IDs'), and specifies the destination ('to a different deck'). It also distinguishes from siblings like 'deck_createDeck' by mentioning deck creation as a side effect rather than the primary purpose.

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?

The description implies usage when needing to relocate cards between decks, but doesn't explicitly state when to use this versus alternatives like 'deck_createDeck' for deck-only creation or 'card_setSpecificValueOfCard' for other card modifications. No exclusions or prerequisites are mentioned.

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

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/ujisati/anki-mcp'

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