Skip to main content
Glama

card_cardsModTime

Retrieve modification timestamps for specific Anki flashcards to track recent changes or updates in your study materials.

Instructions

Returns modification time for each card ID provided. Result is a list of objects with 'cardId' and 'modTime' (timestamp).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYesA list of card IDs.

Implementation Reference

  • The handler function implementing the 'card_cardsModTime' tool (prefixed from 'cardsModTime'). It takes a list of card IDs and returns their modification times by calling the AnkiConnect 'cardsModTime' API.
    @card_mcp.tool(
        name="cardsModTime",
        description="Returns modification time for each card ID provided. Result is a list of objects with 'cardId' and 'modTime' (timestamp).",
    )
    async def get_cards_modification_time_tool(
        cards: Annotated[List[int], Field(description="A list of card IDs.")],
    ) -> List[Dict[str, Any]]:                                                  
        return await anki_call("cardsModTime", cards=cards)
  • Registers the card_mcp service with prefix 'card_', making the tool available as 'card_cardsModTime' under the main AnkiMCP server.
    await anki_mcp.import_server("card", card_mcp)
  • Input schema: list of integers (card IDs). Output: list of dicts with 'cardId' and 'modTime'.
    async def get_cards_modification_time_tool(
        cards: Annotated[List[int], Field(description="A list of card IDs.")],
    ) -> List[Dict[str, Any]]:                                                  
        return await anki_call("cardsModTime", cards=cards)
  • Imports the helper function anki_call used to proxy requests to 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 states the return format but omits critical details like whether this is a read-only operation, if it requires specific permissions, how it handles invalid card IDs, or any rate limits. For a 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?

The description is perfectly concise and front-loaded: it states the core purpose in the first clause and details the output format in the second. Every sentence earns its place with zero wasted words, making it highly efficient for agent comprehension.

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 low complexity (single parameter, no nested objects) and 100% schema coverage, the description is adequate but incomplete. It lacks output schema, so the description must explain return values—which it does partially by specifying the list structure but not full behavioral context like error handling or permissions needed.

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%, so the schema already fully documents the 'cards' parameter. The description adds no additional parameter semantics beyond what's in the schema (e.g., format details, constraints, or examples), meeting the baseline for high schema coverage but not providing extra value.

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 ('Returns modification time') and resource ('for each card ID provided'), distinguishing it from sibling tools like card_cardsInfo or card_findCards that return different card metadata. It precisely defines what the tool does without ambiguity.

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 card_cardsInfo (which might include modTime among other fields) or card_findCards. It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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