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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

statistics.getSummary

statistics_getSummary
Read-only

Retrieve structured Anki collection statistics or summary metrics for a specific deck and its subdecks to inspect study progress and deck performance.

Instructions

Get structured collection statistics or an explicit deck including children.

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

Possible errors: collectionUnavailable, internalError, invalidParams, notFound, 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_getSummary"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckNoDeck (with subdecks): exactly one of {"id": "<deckId>"} or {"name": "<full deck name, e.g. Japanese::Verbs>"}. Omit for the whole collection.
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?

Annotations already cover readOnly/no-destructive/openWorld, and the description adds non-redundant context: collection scope, completion semantics, 'Undo: none', and an enumerated error set including staleSession. That error list is genuinely useful for recovery decisions. The one missing behavioral detail is what the returned statistics actually contain.

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?

Front-loaded with the action and resource, then a labeled metadata block. No filler sentences, and the error list is compressed to bare identifiers rather than prose.

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?

There is no output schema, so the description carries the burden of explaining return values, and 'structured collection statistics' is vague — an agent cannot anticipate what fields come back. Everything else an agent needs to invoke the tool (parameters, scope, safety, error handling) is present.

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 coverage is 100% and the schema already explains the id/name deck union and the session fallback behavior, so the description does not need to compensate. It adds only the 'including children' scoping note, which is already present in the deck property description. 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?

States a specific verb and resource: 'Get structured collection statistics' with optional deck scoping, which is enough to separate it from siblings like statistics_getHtml (HTML output) and statistics_getToday. It stops short of naming those siblings outright, so the differentiation is implied rather than explicit.

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?

'Omit for the whole collection' gives one concrete branching rule for the deck parameter, but there is no statement of when to prefer this over statistics_getHtml, statistics_getToday, or statistics_getReviewDays. Usage is inferable from the word 'structured' but never spelled out.

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