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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

noteTypes.get

noteTypes_get
Read-only

Retrieves an Anki note type's ordered fields, templates, and styling by ID or name so you can inspect its structure.

Instructions

Read ordered fields/templates and styling.

Anki-Connect method noteTypes.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": {
      "noteType": "<noteType>"
    },
    "name": "noteTypes_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
noteTypeYesNote type: exactly one of {"id": "<noteTypeId>"} or {"name": "<note type name, e.g. Basic>"}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover readOnly, non-destructive and closed-world, so the description adds real value on top: it declares the collection scope, that no undo entry is created, and enumerates the concrete failure modes including staleSession, which tells the agent how a bad session parameter manifests. It omits any statement about return shape or size, which keeps it from a 5.

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 behavioral line leads, followed by a compact metadata block and an error list; nothing is padded or repetitive. The terse label-value fragments are efficient, though slightly telegraphic.

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?

For a read tool with no output schema, the description only loosely indicates what comes back ("ordered fields/templates and styling") without describing the response structure. Errors and side-effect status are well covered, so it is adequate but leaves the return value underspecified.

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 schema itself explains the session/staleSession semantics and the id-or-name union. The description adds no additional parameter meaning beyond that, 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: "Read ordered fields/templates and styling" for a note type, which is meaningfully distinct from noteTypes_list or noteTypes_update. It does not name a sibling tool to contrast with, so it stops short of a 5.

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?

There is no when-to-use guidance. "Scope: collection. Effect: read." describes the operation class rather than routing the agent between this and noteTypes_list, noteTypes_getTemplateUsage, or noteTypes_editStructure. The agent must infer that this is the single-note-type detail lookup.

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