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

anki-workflow-mcp

by Gugart43
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Corpus Digest

corpus_digest

Generates a unified triage and coverage report for every corpus file in a deck, helping identify gaps and issues before compiling Anki flashcards.

Instructions

Unified triage + coverage report for all corpus files in the deck.

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": "corpus_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
deck_dirYesAbsolute path to the deck directory (must contain manifesto.json).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and it discloses almost nothing behavioral. It implies a read-only report but never says so, and gives no indication of cost, runtime over 'all corpus files', side effects, or required permissions. The presence of an output schema covers return shape, but not behavior.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is efficient, though bordering on under-specification rather than tightness, which is penalized in the other dimensions.

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?

The output schema means return values need not be described, and one fully documented parameter keeps the surface small. However, with zero annotations and no routing guidance among the many corpus_* siblings, the definition is only minimally sufficient for an agent to choose it confidently.

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?

The single parameter is fully documented in the schema, including the manifesto.json requirement, so the baseline is 3. The description adds no meaning beyond it — it does not say whether deck_dir is scanned recursively, how the deck relates to a corpus root, or what happens when manifesto.json is absent.

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 concrete output (a report) over a concrete resource (all corpus files in the deck) and signals via 'unified triage + coverage' that it merges the two reporting concerns. The verb is nominalized ('digest'/'report'), and it never explicitly names corpus_triage or corpus_coverage as the alternatives it supersedes, so differentiation is inferred rather than stated.

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?

No when-to-use or when-not-to-use guidance. The word 'unified' faintly implies it is the combined alternative to the separate triage and coverage tools, but the agent is given no condition that selects this tool over those siblings, and no prerequisites beyond what the schema states.

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