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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reviewer.startTimer

reviewer_startTimer

Restarts the active reviewer card timer in Anki using the current state token from reviewer_get. Use it when timing must resume for the card currently being reviewed.

Instructions

Restart the active reviewer card timer.

Anki-Connect method reviewer.startTimer. Scope: collection. Effect: gui. Completion: completed. Undo: none.

Possible errors: collectionUnavailable, conflict, internalError, invalidParams, invalidState, 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": {
      "stateToken": "<stateToken>"
    },
    "name": "reviewer_startTimer"
  }
}

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.
stateTokenYesCurrent `stateToken` from `reviewer_get`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Adds real context beyond the annotations: 'Effect: gui' tells the agent this mutates UI/session state, 'Completion: completed' signals synchronous completion, 'Undo: none' warns no rollback exists, and the enumerated error set (staleSession, invalidState, etc.) is actionable. It does not spell out that the elapsed time on the current card is discarded, which is the main semantic consequence of 'restart'.

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?

One-sentence purpose front-loaded, followed by compact labeled metadata lines that each carry distinct information. No filler or restatement.

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 two-parameter GUI-state mutation, the description covers scope, effect class, completion semantics, undo, and error surface. The only omission is any statement of what the call yields (return value is unspecified and there is no output schema).

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 both parameters carry thorough descriptions, including the session-override behavior and the staleSession failure mode. The description adds nothing beyond the schema, so the baseline 3 applies.

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?

States a specific verb+object ('Restart the active reviewer card timer') that is unambiguously distinct from siblings like reviewer_showQuestion, reviewer_showAnswer and reviewer_answer. The Anki-Connect method name is also given for traceability.

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?

Implied usage is clear enough — this applies during an active review session, and the required `stateToken` (from `reviewer_get`) signals the prerequisite. However, it never states when to use this versus alternatives, nor what happens if no card is currently being reviewed, and no sibling is named.

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