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

anki-workflow-mcp

by Gugart43
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Deck Audit

deck_audit

Audits an Anki deck directory to detect orphan and phantom IDs, verify batch integrity, and report coverage for reliable deck health checks.

Instructions

Full deck health audit: orphan IDs, phantom IDs, batch integrity, and coverage summary.

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": {
      "deck_dir": "<deck_dir>"
    },
    "name": "deck_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
deck_dirYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Audit' strongly implies a read-only diagnostic and the listed checks describe the scope of inspection, which is genuinely useful. However, it never states outright that nothing is mutated, what access the deck directory requires, or how long/heavy the scan is.

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?

A single compact sentence that front-loads the scope ('Full deck health audit') and then lists the concrete checks. Every clause earns its place with no filler.

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?

Because an output schema exists, the description is not obligated to explain return values, and the enumeration of checks tells the agent what the audit covers. Still, for a tool with one undocumented required parameter and no annotations, the definition leaves key operational facts (input meaning, read-only nature) unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, deck_dir, with 0% schema description coverage, and the description never mentions it. The agent cannot tell from either source whether it is a filesystem path, a deck identifier, or a project root. With only one param, a brief clarification would have fully compensated for the schema gap.

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 ('deck health audit') and enumerates the four checks: orphan IDs, phantom IDs, batch integrity, coverage summary. An agent knows exactly what the tool inspects. It does not explicitly contrast itself with nearby diagnostics like corpus_coverage or pipeline_gate_check, so it stops short of a 5.

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

Usage Guidelines2/5

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

'Full deck health audit' implies the situation (validate a deck's integrity), but there is no explicit when-to-use statement, no prerequisites, and no named alternative or exclusion. The agent must infer that this is a pre-flight/diagnostic step rather than being told.

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