Skip to main content
Glama

card_suspend

Suspend specific Anki flashcards to temporarily pause their review schedule, helping you manage study sessions by focusing on active cards.

Instructions

Suspends the specified cards. Returns true on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYesA list of card IDs to suspend.

Implementation Reference

  • Handler function for the 'suspend' tool (prefixed to 'card_suspend' in main MCP) that suspends Anki cards by calling the AnkiConnect API.
    @card_mcp.tool(
        name="suspend", description="Suspends the specified cards. Returns true on success."
    )
    async def suspend_cards_tool(
        cards: Annotated[List[int], Field(description="A list of card IDs to suspend.")],
    ) -> bool:
        return await anki_call("suspend", cards=cards)
  • Registers the card service tools with 'card_' prefix, making 'suspend' available as 'card_suspend'.
    await anki_mcp.import_server("card", card_mcp)
  • Utility function that makes HTTP POST requests to AnkiConnect API, used by card_suspend to invoke the 'suspend' action.
    async def anki_call(action: str, **params: Any) -> Any:
        async with httpx.AsyncClient() as client:
            payload = {"action": action, "version": 6, "params": params}
            result = await client.post(ANKICONNECT_URL, json=payload)
            result.raise_for_status()                                      
            result_json = result.json()
            error = result_json.get("error")
            if error:
                raise Exception(f"AnkiConnect error for action '{action}': {error}")
            response = result_json.get("result")
                                                                 
                                                                                                         
                                                                                            
            if "result" in result_json:
                return response
            return result_json                                                                        
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'suspends' cards and 'returns true on success', which implies a mutation with a boolean outcome. However, it lacks critical details: what 'suspend' means operationally (e.g., hides cards, pauses reviews), whether it's reversible, permission requirements, error handling, or side effects. For a mutation tool with zero annotation coverage, this is a significant gap.

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 very concise—two short sentences that state the action and outcome. It's front-loaded with the primary purpose. However, the brevity comes at the cost of completeness, as it omits important contextual details. Every sentence earns its place, but more sentences would be beneficial for clarity.

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 the complexity (a mutation tool that suspends cards), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'suspend' entails, potential impacts, or error scenarios. The return value ('true on success') is mentioned, but without an output schema, more detail on failure modes or other return data would help. For a tool with behavioral implications, this is inadequate.

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 input schema has 100% description coverage, with the 'cards' parameter documented as 'A list of card IDs to suspend'. The description adds no additional parameter semantics beyond what the schema provides. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description, which applies here.

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 ('Suspends') and the resource ('the specified cards'), making the purpose immediately understandable. It distinguishes from sibling tools like 'card_unsuspend' (opposite action) and 'card_suspended' (likely a status check), though it doesn't explicitly mention these alternatives. The description is specific but could be more precise about what 'suspend' means in this context.

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. It doesn't mention prerequisites (e.g., card IDs must exist), exclusions, or compare to siblings like 'card_unsuspend' or 'card_setSpecificValueOfCard'. The agent must infer usage from the tool name and context alone, which is insufficient for optimal selection.

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