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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

statistics.getReviewDays

statistics_getReviewDays
Read-only

List every nonempty historical review day from an Anki collection, newest first, using native graph day conventions to inspect study activity over time.

Instructions

Return all nonempty historical review days in descending date order using native graph day conventions.

Anki-Connect method statistics.getReviewDays. Scope: collection. Effect: read. Completion: completed. Undo: none.

Possible errors: collectionUnavailable, internalError, invalidParams, staleSession.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "statistics_getReviewDays"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that empty days are excluded, that ordering is descending, that days follow native graph conventions, that Undo is not applicable, and it enumerates the four possible error codes. It stops short of describing volume or pagination behavior for large collections, but the added context is substantial.

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 primary behavior is front-loaded in the first sentence, and the remaining metadata is terse and scannable. The scope/effect/completion/undo line reads as boilerplate but each token is informative and short.

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?

With no output schema, the description still conveys the return content (days) and ordering, plus the failure modes an agent may need to handle. For a zero-required-param read tool this is nearly complete; only the return value's exact structure/shape is left implicit.

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% and the single optional session parameter is fully explained in the schema, including the staleSession trade-off. The description adds nothing parameter-specific beyond that, so baseline 3 applies.

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 gives a specific verb and resource ('Return all nonempty historical review days') plus ordering and day convention. It is distinguishable from statistics_getToday, but it never explicitly contrasts with that sibling or with statistics_getSummary, which also touch review statistics.

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?

Usage is implied by 'historical' versus getToday's 'today', but the description never states when to choose this over statistics_getToday or statistics_getSummary. The scope/effect/completion metadata line gives some operational framing but no explicit when-not-to-use guidance.

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