Skip to main content
Glama
Sign In
anki-connect-mcp

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

scheduling.setDueDate

scheduling_setDueDate

Set Anki card due dates using native day or range syntax, including today, tomorrow, random ranges, and optional interval updates.

Instructions

Set due dates using Anki native days/range syntax.

Anki-Connect method scheduling.setDueDate. Scope: collection. Effect: write. Completion: completed. Undo: perItem.

Possible errors: collectionUnavailable, editorConflict, internalError, invalidParams, notFound, staleSession, validationFailed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cardIds": "<cardIds>",
      "days": "<days>"
    },
    "name": "scheduling_setDueDate"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesAnki due-date syntax: `0` = today, `1` = tomorrow, `3-7` = random day in the range; append `!` (e.g. `5!`) to also set the interval.
cardIdsYesCard IDs (decimal string, e.g. "1700000000001").
sessionNoOptional. Collection session ID: the `session` field returned by `collection_get`. Usually omit it — the server then uses the session current at the time of the call. Pass it to make the call fail with `staleSession` instead of acting on a different profile/collection than the one your IDs, cursors and tokens came from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Adds substantial behavior beyond annotations: collection scope, write effect, completion semantics, per-item undo, and a concrete list of possible errors. It does not explain the response shape or the consequences of overwriting existing due dates, but annotations already cover the basic safety profile.

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 compact and front-loaded, with useful metadata and error names. The compressed labels such as 'Completion' and 'Undo' are terse but still readable; little wording is wasted.

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?

For a write tool with no output schema and fully documented parameters, it covers scope, effect, undo granularity, and common errors. It could be more complete by describing the expected return or the scheduling consequences of overwriting existing due dates.

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%, including detailed days syntax, cardIds format, and session behavior. The description adds only a general pointer to Anki native syntax, so the schema carries the parameter semantics.

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?

States a specific verb and resource: setting due dates for cards using Anki-native syntax. It is clearly distinguishable from read-oriented siblings like scheduling_getDue, though it does not explicitly name alternatives such as scheduling_reset.

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?

Provides scope and write-effect metadata but no explicit when-to-use guidance, prerequisites, or comparison against related scheduling tools such as scheduling_reset or scheduling_getDue. The agent must infer usage from the name and method mapping.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools