Skip to main content
Glama
deenesjakoruzh
ujisati

anki-mcp

by ujisati
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

note_updateNote

Modify fields and tags of an existing Anki flashcard note to update content or organization.

Instructions

Modifies the fields and/or tags of an existing note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesNote object to update. Must include 'id'. Can include 'fields', 'tags', 'audio', 'video', 'picture'.

Implementation Reference

  • src/anki_mcp/note_service.py:118-130 (handler)
    Handler function executing the tool logic for note_updateNote, calling AnkiConnect's updateNote API.
    @note_mcp.tool(
    name="updateNote",
    description="Modifies the fields and/or tags of an existing note.",
)
async def update_note_tool(
    note: Annotated[
        Dict[str, Any],
        Field(
            description="Note object to update. Must include 'id'. Can include 'fields', 'tags', 'audio', 'video', 'picture'."
        ),
    ],
) -> None:
    return await anki_call("updateNote", note=note)
  • src/anki_mcp/__init__.py:24-24 (registration)
    Registers the note_mcp (AnkiNoteService) tools with 'note_' prefix into the main anki_mcp, making 'updateNote' available as 'note_updateNote'.
    await anki_mcp.import_server("note", note_mcp)
  • src/anki_mcp/note_service.py:123-128 (schema)
    Pydantic schema/validation for the input parameter 'note' of the tool.
    note: Annotated[
    Dict[str, Any],
    Field(
        description="Note object to update. Must include 'id'. Can include 'fields', 'tags', 'audio', 'video', 'picture'."
    ),
],
  • src/anki_mcp/note_service.py:8-8 (registration)
    Creates the FastMCP instance for note service tools where note_updateNote (as updateNote) is defined.
    note_mcp = FastMCP(name="AnkiNoteService")

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool modifies existing notes, implying a mutation, but lacks details on permissions, side effects, error handling, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error conditions, and what the modification entails beyond basic field/tag updates, leaving significant gaps in understanding how to use the tool effectively.

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 input schema has 100% description coverage, documenting the single 'note' parameter with its structure and required 'id'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 clearly states the action ('modifies') and resource ('fields and/or tags of an existing note'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'note_updateNoteFields' or 'note_addTags', which appear to handle similar operations, leaving some ambiguity about when to choose this tool over those alternatives.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools such as 'note_updateNoteFields' and 'note_addTags' available, there is no indication of specific use cases, prerequisites, or exclusions, leaving the agent without clear direction for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ujisati/anki-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server