Skip to main content
Glama
samefarrar

MCP-AnkiConnect

by samefarrar
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

reschedule_cards

Modify scheduling of Anki cards: set due dates, reset to new queue, or move to relearn.

Instructions

Manipulate the scheduling state of one or more cards.

Modes:
- `set_due`: Set the cards' due date. Requires `due`. Accepts AnkiConnect's
  `setDueDate` spec:
    * "1"   → due 1 day from now
    * "1-7" → randomly due between 1 and 7 days from now
    * "3!"  → due in 3 days AND reset interval to 3
- `forget`: Reset cards to the "new" queue (re-enters the learning pipeline).
- `relearn`: Move cards into the relearning queue.

Args:
    card_ids: Card IDs to reschedule.
    mode: One of "set_due", "forget", "relearn".
    due: Required for `mode="set_due"`; ignored otherwise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idsYes
modeYes
dueNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explains the effects of each mode (e.g., forget resets to new queue, relearn moves to relearning queue) but does not mention potential side effects or permissions.

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 concise and well-structured, front-loading the purpose and using clear formatting for modes and args without any unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all parameters and modes effectively. Given the existence of an output schema, return values need not be explained. However, it could provide more context on when to choose each mode.

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

Parameters5/5

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

Despite 0% schema description coverage, the description explains all three parameters in detail, especially the due format spec, which adds significant meaning beyond the schema's type definitions.

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 tool manipulates scheduling state of cards, with specific modes (set_due, forget, relearn) that distinguish it from sibling tools like add_note or change_deck.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides detailed guidance on modes and the due format, but does not explicitly compare to sibling tools or state when not to use it.

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/samefarrar/mcp-ankiconnect'

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