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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reviewer.playAudio

reviewer_playAudio

Replays the audio for the current Anki review card side, helping users hear pronunciation or media again without leaving the review session.

Instructions

Replay audio for the current side.

Anki-Connect method reviewer.playAudio. 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_playAudio"
  }
}

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.2/5.0
Behavior5/5

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

It adds substantial behavioral context beyond the annotations: collection scope, GUI effect, no undo, completion behavior, and a named list of possible errors. This gives the agent useful operational details while remaining consistent with the non-destructive annotation.

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 action is front-loaded and the supporting metadata is compact and clearly structured. The line 'Completion: completed' is slightly redundant, but the overall definition avoids unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple action tool with full schema coverage, annotations, and no output schema, the description covers scope, effect, undo behavior, and error conditions. Nothing essential is missing for an agent to invoke it correctly.

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 schema already explains both session and stateToken in detail. The description adds no additional parameter-specific semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: 'Replay audio for the current side.' It clearly distinguishes this from other reviewer tools such as reviewer_showQuestion and reviewer_showAnswer, which navigate rather than play audio.

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 implies usage during a review when audio needs to be replayed, but it does not explicitly state when to call this tool versus alternatives or note preconditions such as an active review session. The guidance is therefore present only by implication.

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