Skip to main content
Glama
slide-anki-mcp
by 2Mesh

export_anki

Write validated flashcards to a new Anki-importable .tsv file only after every card passes checks; includes slide citations and skips duplicate cards.

Instructions

Write cards to a new Anki-importable .tsv, only if every card passes check_cards.

out_path must end with .tsv, be in an existing folder, and must not exist yet. The evidence quote and slide number are written at the end of each answer. Exact duplicates (same front and back) are written once; the indexes of the skipped copies are listed in 'duplicates_skipped'.

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": {
      "pdf_path": "<pdf_path>",
      "cards": "<cards>",
      "out_path": "<out_path>"
    },
    "name": "export_anki"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsYes
out_pathYes
pdf_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses all-or-nothing gating via check_cards, that out_path must be new and in an existing folder, deduplication by front/back, and that skipped indexes surface in 'duplicates_skipped'. It omits what happens on validation failure (partial file left behind?) and permission/overwrite errors, which keeps it below a 5.

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?

Four dense sentences, front-loaded with the action and gating condition, with no filler. Minor ambiguity in 'written at the end of each answer' (answer = card back?) costs it a point.

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 mutation tool with no annotations and no output schema, the description covers failure precondition, path rules, dedup behavior, and a named return field. The unexplained pdf_path parameter is the main remaining gap.

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 0%, so all three required parameters depend on the description. out_path is covered in detail and cards is partially characterized (front/back duplicates), but pdf_path is never explained—an agent must guess why a PDF is required for a TSV export.

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 and resource ('Write cards to a new Anki-importable .tsv') plus the gating condition ('only if every card passes check_cards'), which cleanly separates it from the sibling check_cards, a validator rather than a writer.

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

Usage Guidelines4/5

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

Gives a clear precondition for invocation (all cards must pass check_cards) and hard constraints on the destination path. It doesn't state what to do when validation fails or point to any alternative beyond the implied check_cards prerequisite, but the usage context is unambiguous.

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