Skip to main content
Glama
Sign In
@lifeng688/anki-mcp

@lifeng688/anki-mcp

by guanweiqiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_note

Add a single flashcard to a specific Anki deck by specifying the note model, field values, and optional tags. Control duplicate prevention with the allowDuplicate option.

Instructions

Add a single note (flashcard) to Anki.

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": {
      "deckName": "<deckName>",
      "modelName": "<modelName>",
      "fields": "<fields>"
    },
    "name": "add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckNameYesTarget deck name.
modelNameYesNote model name.
fieldsYesField values as key-value pairs.
tagsNoTags to assign to the note.
allowDuplicateNoWhether to allow duplicates. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'add' (mutation) but lacks details on permissions, side effects, or what happens on duplicate—even though an 'allowDuplicate' parameter exists. The description does not compensate for the missing annotation context.

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, front-loaded sentence with no unnecessary words. Every word earns its place by stating the action, object, and context.

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 parameter schema is complete, but there is no output schema and the description lacks behavioral context (e.g., duplicate handling, error scenarios). For a mutation tool, this is minimally adequate but not comprehensive.

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 has 100% parameter description coverage, so the baseline is 3. The description adds no extra meaning beyond the tool's purpose; all parameter semantics are already covered in the schema.

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?

The description clearly states the verb 'Add', the resource 'single note (flashcard)', and the destination 'Anki'. It distinctly separates from sibling add_notes (plural) and update_note_fields.

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

Usage Guidelines3/5

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

The description implies use for a single note, but provides no explicit guidance on when to use this tool versus alternatives like add_notes or when duplicates are allowed. No context about prerequisites or excluded use cases.

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