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

@lifeng688/anki-mcp

by guanweiqiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_notes

Batch add multiple notes to Anki decks with optional duplicate control and dry-run preview.

Instructions

Batch add multiple notes to Anki. Supports dryRun for preview.

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>",
      "notes": "<notes>"
    },
    "name": "add_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckNameYesTarget deck name.
modelNameYesNote model name.
notesYesArray of note objects with fields and optional tags.
allowDuplicateNoWhether to allow duplicates. Default false.
dryRunNoIf true, only validate and preview without writing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions dryRun for preview, but fails to disclose behavioral traits like side effects (creation), error handling, or performance implications for batch operations.

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 extremely concise with one sentence. It is front-loaded with the core purpose. However, it could be slightly longer to include essential usage guidance without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a batch operation with 5 parameters and no output schema, the description is insufficient. It omits details on return values, error behavior, and performance considerations.

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 baseline is 3. The description does not add meaning beyond the schema; it merely restates 'dryRun' which is already described 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 tool's purpose: batch adding multiple notes to Anki. The verb 'add' and resource 'notes' are specific, and it distinguishes from the sibling 'add_note' by indicating batch operation.

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives (like 'add_note' for single notes) or any prerequisites or constraints.

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