Skip to main content
Glama
Sign In
anki-connect-mcp

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notes.get

notes_get
Read-only

Retrieve an Anki note by ID via Anki-Connect, including card IDs, and get an empty cardIds array for cardless notes. Use it to inspect note details or verify note data.

Instructions

Get a note, including an empty cardIds array for cardless notes.

Anki-Connect method notes.get. Scope: collection. Effect: read. Completion: completed. Undo: none.

Possible errors: collectionUnavailable, internalError, invalidParams, notFound, staleSession.

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": {
      "id": "<id>"
    },
    "name": "notes_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNote ID (decimal string, e.g. "1700000000001").
sessionNoOptional. Collection session ID: the `session` field returned by `collection_get`. Usually omit it — the server then uses the session current at the time of the call. Pass it to make the call fail with `staleSession` instead of acting on a different profile/collection than the one your IDs, cursors and tokens came from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that the description adds useful operational context: collection scope, a completed-effect statement, undo=none, and an enumerated error set including notFound and staleSession, which helps an agent plan failure handling.

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 purpose sentence is front-loaded and followed by a compact metadata block (scope, effect, completion, undo, errors). Every line is short and useful, though the metadata block reads as templated boilerplate rather than tailored guidance.

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

Completeness4/5

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

For a simple read-only single-item fetch with full annotation coverage and a fully documented two-parameter schema, the definition covers purpose, scope, side-effect posture and failure modes. With no output schema present, the return shape is only partially described (cardIds mentioned, other fields unstated), which is the main remaining gap.

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%, and the `session` parameter is explained in depth inside the schema itself, so the schema does the heavy lifting. The description adds no parameter-level meaning (e.g. what id formats are accepted beyond the pattern already in the schema), so the baseline 3 applies.

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?

States a specific verb and resource ("Get a note") and adds a concrete return detail (empty cardIds array for cardless notes). It does not distinguish itself from close siblings like notes_getMany or notes_search, so the agent must infer the single-vs-multiple split.

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?

Usage is only implied by the verb and the required single `id`; there is no explicit guidance such as when to prefer this over notes_getMany for batches or notes_search for lookup by query. The stated scope (collection) gives some context but does not route the agent between alternatives.

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