Skip to main content
Glama

deck_deckNames

Retrieve all deck names from Anki to view and manage your flashcard collections efficiently.

Instructions

Gets the complete list of deck names for the current user. Returns a list of deck names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'deck_deckNames' tool (internally named 'deckNames' in deck_mcp). It calls anki_call('deckNames') to fetch and return the list of deck names.
    @deck_mcp.tool(
        name="deckNames",
        description="Gets the complete list of deck names for the current user. Returns a list of deck names.",
    )
    async def list_deck_names_tool() -> List[str]:
        return await anki_call("deckNames")
  • Registers the deck_mcp server under the 'deck' prefix in the main anki_mcp, making tools like 'deckNames' available as 'deck_deckNames'.
    await anki_mcp.import_server("deck", deck_mcp)
  • Creates the FastMCP instance 'deck_mcp' (named 'AnkiDeckService') to which the deck tools, including 'deckNames', are attached.
    deck_mcp = FastMCP(name="AnkiDeckService")
  • Imports the anki_call helper function used by the deck_deckNames handler to invoke the underlying AnkiConnect API.
    from .common import anki_call
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 that it returns a list of deck names, which is helpful, but fails to address potential behaviors like error handling, rate limits, authentication requirements, or whether the list is sorted or paginated. This leaves significant gaps in understanding how the tool operates.

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 two concise sentences that directly state the action and the return value without any fluff. It is front-loaded with the core purpose and efficiently communicates the essential information, making it easy for an agent to parse quickly.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose and return type, but lacks details on authentication, error cases, or differentiation from siblings, which could be important for an agent to use it correctly in a broader context.

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?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any, earning a baseline score of 4 for not introducing confusion or redundancy.

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 verb 'gets' and resource 'complete list of deck names for the current user', making the purpose specific and understandable. However, it doesn't explicitly differentiate from its sibling 'deck_deckNamesAndIds', which likely returns names with IDs, leaving some ambiguity about when to choose one over the other.

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_deckNamesAndIds' or other deck-related tools. It lacks context about prerequisites, such as whether the user needs to be authenticated or if there are any limitations, leaving the agent without usage direction.

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