Skip to main content
Glama
Sign In
Mousetail

Mousetail

by listfold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_note

Add a flashcard to Anki by specifying deck, note type, and field values. The tool creates a note which generates cards according to the note type template.

Instructions

Create a new note (flashcard) in Anki. A note generates one or more cards based on the note type template.

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": {
      "deck_name": "<deck_name>",
      "note_type_name": "<note_type_name>",
      "fields": "<fields>"
    },
    "name": "create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
deck_nameYesName of the deck where the note should be added
note_type_nameYesName of the note type (e.g., 'Basic', 'Cloze')
fieldsYesField name to value mapping (e.g., {'Front': 'Question', 'Back': 'Answer'})
tagsNoOptional list of tags
collection_pathNoPath to collection file (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It states the note generates cards based on template but lacks details on side effects, validation, or prerequisites. Moderate transparency.

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?

The description is highly concise, consisting of two sentences with no wasted words. The first sentence front-loads the primary purpose, and the second adds relevant 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?

Given the tool's complexity (5 parameters, nested objects, no output schema) and lack of annotations, the description is informative but incomplete. It omits return values, error conditions, and prerequisites, making it adequate but not thorough.

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 parameters are fully described in the schema. The description adds no additional meaning beyond the schema, warranting a baseline score of 3.

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 'Create', the resource 'note (flashcard)', and the context 'Anki'. It also explains the effect of generating cards, distinguishing it from sibling tools like create_deck or update_note.

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 usage for creating new notes but does not explicitly provide when-to-use guidance, when-not-to-use conditions, or alternatives. Given sibling tools, the context is implicit but not explicit.

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