Skip to main content
Glama
jasperket

Clanki

by jasperket
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create-card

Create a new flashcard in an existing Anki deck. Supports HTML formatting and attaches images or audio from URLs to the front or back.

Instructions

Create a new note in a specified deck. Supports HTML formatting in text fields. You can attach multiple images and audio files from URLs - they will be automatically downloaded and embedded in the note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
backYesBack side content of the note (supports HTML formatting)
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.
frontYesFront side content of the note (supports HTML formatting)
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 of the note. Audio will be downloaded and can be played in Anki.
backImagesNoOptional array of image URLs to embed on the back of the note. Images will be downloaded and attached automatically.
frontAudioNoOptional array of audio file URLs to attach to the front of the note. Audio will be downloaded and can be played in Anki.
frontImagesNoOptional array of image URLs to embed on the front of the note. 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?

There are no annotations, so the description carries the behavioral disclosure burden. It does disclose meaningful behavior: HTML support, automatic downloading and embedding of media from URLs. However, it does not mention what happens on success or failure, whether a card ID is returned, or any side effects beyond creation. For a mutation tool with no annotations, richer behavioral disclosure would be expected.

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 description is compact and front-loaded with the core action. It consists of three sentences with no obvious filler. It could be slightly sharper by naming the front/back text fields instead of 'text fields,' but it is generally well-structured.

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?

Given the 8 parameters and no output schema, the description is adequate but incomplete for fully informed invocation. The rich schema covers parameter details, but the description does not clarify the expected return value, error behavior, or how this tool differs from the bulk and cloze siblings. That leaves some decision-making burden on the agent.

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 schema already documents all 8 parameters with 100% coverage, so the baseline is 3. The description's mention of HTML and URL-based media roughly mirrors the schema's per-parameter descriptions and adds little new semantic meaning beyond what is already structured.

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 clear verb and resource: 'Create a new note in a specified deck.' It also adds useful scope by mentioning HTML formatting and media attachment. It does not explicitly distinguish itself from siblings like create-cloze-card or create-cards-bulk, though the required front/back fields and name imply a standard note.

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 gives no guidance about when to use this tool versus alternatives such as create-cloze-card, create-cards-bulk, or update-card. There are no usage conditions, exclusions, or prerequisites stated in the description itself; the deck-existence prerequisite appears only in the schema, not in the tool description.

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