Skip to main content
Glama

deck_saveDeckConfig

Save custom deck configuration settings in Anki to personalize study parameters and optimize flashcard learning workflows.

Instructions

Saves the given configuration group. Returns true on success, false otherwise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYesThe deck configuration object to save. Must include an 'id'.

Implementation Reference

  • The tool handler implementation including decorator, input schema via Pydantic Annotated/Field, and logic that proxies to AnkiConnect's saveDeckConfig API.
    @deck_mcp.tool(
        name="saveDeckConfig",
        description="Saves the given configuration group. Returns true on success, false otherwise.",
    )
    async def save_deck_config_tool(
        config: Annotated[
            Dict[str, Any],
            Field(
                description="The deck configuration object to save. Must include an 'id'."
            ),
        ],
    ) -> bool:
        return await anki_call("saveDeckConfig", config=config)
  • Top-level registration that imports all deck tools with 'deck_' prefix into the main Anki MCP server, exposing 'saveDeckConfig' as 'deck_saveDeckConfig'.
    await anki_mcp.import_server("deck", deck_mcp)
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 mentions the return value (true/false on success/failure) but lacks critical details: whether this is a mutation (implied by 'Saves'), permission requirements, error conditions, or side effects. This is inadequate for a tool that modifies data.

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?

The description is two concise sentences with zero waste, front-loading the core action. However, it could be slightly more structured by explicitly stating this updates existing configurations, but it's efficient as-is.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on permissions, error handling, what 'configuration group' entails, or how it differs from sibling tools. The return value is mentioned, but behavioral context is insufficient.

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 100%, with the schema fully documenting the 'config' parameter (including the requirement for an 'id'). The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline for high 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 ('Saves') and resource ('configuration group'), distinguishing it from siblings like deck_createDeck (creates new decks) and deck_getDeckConfig (retrieves configuration). However, it doesn't specify that this is for updating existing deck configurations, which would make it more precise.

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 like deck_createDeck or deck_changeDeck. It doesn't mention prerequisites (e.g., that the config must already exist) or exclusions, leaving the agent to infer usage from context 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

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