Skip to main content
Glama
Sign In
Mousetail

Mousetail

by listfold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_note

Update fields and tags of existing Anki notes by specifying note ID and optional field values, tags, or collection path.

Instructions

Update an existing note's fields and/or tags

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": {
      "note_id": "<note_id>"
    },
    "name": "update_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYesID of the note to update
fieldsNoField name to value mapping for fields to update
tagsNoNew list of tags (replaces existing tags)
collection_pathNoPath to collection file (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.1/5.0
Behavior2/5

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

The description does not disclose whether the note must exist, how errors are handled, or whether fields merge or replace. With no annotations, the description carries the burden but provides minimal behavioral context.

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?

One sentence, efficient and to the point. No wasted words, though it could be slightly improved by front-loading the action.

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?

No output schema or annotations. The description does not indicate what the tool returns (e.g., updated note or success status). For a mutation tool with no return info, this is insufficient.

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 description coverage is 100%, so baseline is 3. The summary 'fields and/or tags' adds minimal value beyond the schema, which already describes each parameter.

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 action (update), the resource (existing note), and the scope (fields and/or tags), differentiating it from create_note and get_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?

No guidance is provided on when to use this tool vs alternatives like create_note or when not to use it. No context for prerequisites or conditions.

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