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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

scheduling.getDue

scheduling_getDue
Read-only

Checks whether an Anki card is due now by queue, excluding suspended, buried, and learn-ahead cards, and reports availability without needing review history.

Instructions

Inspect queue-aware due eligibility without requiring history.

dueNow excludes learn-ahead and suspended/buried queues. New cards are available but have no timed due obligation. available ignores daily deck limits; includeLearnAhead expands learning availability only.

Anki-Connect method scheduling.getDue. Scope: collection. Effect: read. Completion: completed. Undo: none.

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

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": {
      "cardId": "<cardId>"
    },
    "name": "scheduling_getDue"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesCard ID (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.
includeLearnAheadNoTreat learning cards within the learn-ahead limit as due. Default false.

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?

Annotations already establish readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description still adds genuinely new behavioral facts: method provenance (Anki-Connect scheduling.getDue), collection scope, "Undo: none", completion state, and an enumerated error set including staleSession and notFound. Missing only is any statement about result shape or performance characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose and the metadata block at the end is scannable. The middle paragraph, however, is a set of subject-less fragments ("dueNow excludes...", "available ignores...") that reference output fields the reader has not been told about, costing clarity for the space saved.

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?

With no output schema, the description is the only source for what the call returns, yet it introduces dueNow and available as if they were already defined and never says how they differ structurally. Scope, effect, undo, and errors are all covered, so it is adequate but leaves a real gap around the returned payload.

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 a thorough explanation of `session` and its staleSession failure mode, so the schema carries the load and baseline 3 applies. The description's only extra signal is that includeLearnAhead "expands learning availability only", a small nuance not fully spelled out in the schema.

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?

Names a specific action and object: "Inspect queue-aware due eligibility", with the added qualifier that it works "without requiring history", which is a meaningful distinguisher from history-based computations. It does not, however, name or contrast with the nearby siblings (scheduling_get, scheduling_getQueue, scheduling_predict), so an agent must still infer which scheduling query to pick.

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

Usage Guidelines3/5

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

The description gives real decision content — dueNow excludes learn-ahead and suspended/buried queues, available ignores daily deck limits, includeLearnAhead expands only learning availability — which implies when its answers differ from alternatives. But it never states explicitly when to call this instead of scheduling_get or scheduling_getQueue, so the choice is left to inference.

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