Skip to main content
Glama
jasperket

Clanki

by jasperket
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create-cloze-card

Create cloze deletion flashcards in any Anki deck using {{c1::}} syntax. Add HTML formatting, images, and audio files to build richer study materials.

Instructions

Create a new cloze note in a specified deck. Use {{c1::text}} syntax for cloze deletions (e.g., {{c1::Paris}} is the capital of France). Supports HTML formatting and can attach multiple images and audio files from URLs - they will be automatically downloaded and embedded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags for the note. A tag cannot contain a space (Anki splits it into two tags) or a tab or newline (Anki removes it) - use organic_chemistry or organic::chemistry for a hierarchy.
textYesText containing cloze deletions using {{c1::text}} syntax. Supports HTML formatting. Use {{c1::word}}, {{c2::word}}, etc. for multiple deletions.
deckNameYesName of the deck to add the note to. The deck must already exist - use create-deck first if it does not. A `::` in the name means a nested deck: `Biology::Cells` is a deck named Cells inside a deck named Biology. There is no way to name a single deck literally `Biology::Cells`.
backAudioNoOptional array of audio file URLs to attach to the back extra field. Audio will be downloaded and can be played in Anki.
backExtraNoOptional extra information to show on the back of the card (supports HTML formatting)
textAudioNoOptional array of audio file URLs to attach to the main text field. Audio will be downloaded and can be played in Anki.
backImagesNoOptional array of image URLs to embed in the back extra field. Images will be downloaded and attached automatically.
textImagesNoOptional array of image URLs to embed in the main text field. Images will be downloaded and attached automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose the key non-obvious behavior: media from URLs is 'automatically downloaded and embedded.' However, this largely repeats what the schema parameter descriptions already state, and it omits other behaviors an agent might need, such as duplicate-creation consequences or deletion of previous notes.

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?

Two sentences with the primary purpose and syntax example front-loaded. The example ({{c1::Paris}} is the capital of France) earns its place, and the media-handling sentence is compact. Slight redundancy with schema param descriptions prevents a 5.

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?

For an 8-parameter creation tool with no annotations and no output schema, the description covers the core cloze workflow adequately and the schema richly documents every parameter. It is incomplete in that it doesn't address return values, duplicate-creation behavior, or how this differs from the bulk sibling, though schema richness compensates for much of the 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 coverage is 100%, so the baseline is 3. The description adds marginal value by demonstrating the {{c1::text}} syntax pattern for the text parameter, but it adds nothing about deckName, tags, audio, or image parameters beyond what the schema already documents.

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?

The description states a specific verb and resource ('Create a new cloze note in a specified deck') and the cloze-deletion syntax example makes it clearly distinct from the sibling create-card. However, it does not differentiate itself from create-cloze-cards-bulk, so it falls just short of full sibling distinction.

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?

The description explains HOW to use the tool (cloze syntax, HTML support) but gives no guidance on WHEN to choose it over alternatives like create-card, create-cloze-cards-bulk, or update-cloze-card. The only usage routing (use create-deck first) lives in the schema, not the description, so an agent gets no explicit selection criteria from the description itself.

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