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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

noteTypes.getTemplateUsage

noteTypes_getTemplateUsage
Read-only

Inspect a note type's question/answer templates to identify referenced fields in first-reference order, including conditional and filtered replacement fields.

Instructions

Inspect question/answer template field references.

Python adapter mirrors native token rules because the parsed tree is not exposed to Python. Includes conditional fields and filtered replacements, ignores HTML comments and special fields, supports legacy alternate delimiters, and returns real fields once in first-reference order.

Anki-Connect method noteTypes.getTemplateUsage. Scope: collection. Effect: read. Completion: completed. Undo: none.

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

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_getTemplateUsage"
  }
}

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

A3.6/5.0
Behavior4/5

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

The annotations already establish read-only safety, and the description adds meaningful behavior: conditional fields and filtered replacements are included, HTML comments and special fields are ignored, legacy alternate delimiters are supported, and fields are returned once in first-reference order. It also lists possible errors and states scope/effect. The main gap is the exact shape of the returned data.

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 description is front-loaded with purpose, followed by behavioral notes, then structured metadata and errors. It is somewhat dense and includes implementation-oriented detail about the Python adapter, but most sentences carry useful information and there is little redundancy.

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 template-parsing tool with no output schema, the description should explain the return value more concretely. It says fields are returned once in first-reference order, which helps, but it does not clarify the data structure, field metadata, or what happens for templates with no field references.

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 both the session and noteType parameters are already well documented in the schema. The description adds no meaning about parameter values, formats, or edge cases beyond what the schema provides, 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?

The description uses a specific verb and resource: 'Inspect question/answer template field references.' That is clearly narrower than sibling tools such as noteTypes_get or noteTypes_list, but the description does not explicitly contrast itself with those siblings.

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 purpose implies when the tool is useful, but there is no explicit 'use this when' guidance, no exclusions, and no named alternative such as noteTypes_get. The agent must infer the selection criteria from the single purpose sentence.

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