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

anki-workflow-mcp

by Gugart43
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Taxonomy Check

taxonomy_check

Validates space-separated tags against the Manifesto taxonomy, returning ok, unregistered, depth, or format results per tag so Anki decks stay correctly categorized.

Instructions

Check tags against the Manifesto taxonomy. tags: space-separated list. Returns ok/unregistered/depth/format per tag.

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": {
      "deck_dir": "<deck_dir>",
      "tags": "<tags>"
    },
    "name": "taxonomy_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYes
deck_dirYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the outcome categories (ok/unregistered/depth/format per tag), which implies a non-mutating validation, but it never states that it is read-only, what permissions or corpus state it requires, or why a deck directory is needed for a taxonomy check.

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?

Three short sentences with the core action front-loaded and no filler. The terse 'tags: space-separated list' phrasing is 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?

An output schema exists, so the return-value summary is a bonus rather than a necessity, and the tool is simple with only two parameters. However, with no annotations and deck_dir undocumented, the definition leaves an agent guessing about the deck's role and about safety before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must document both parameters. It explains the tags format ('space-separated list'), which is genuinely useful, but deck_dir is left entirely unexplained, leaving a required parameter whose role is unclear in a taxonomy validation call.

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 gives a specific verb and resource: check tags against the Manifesto taxonomy. That is clearly a validation operation and is distinguishable from mutation siblings like batch_auto_fix or manifesto_commit. It stops short of naming a contrasting sibling, so it is not 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 statement of when to use this tool versus alternatives, no prerequisite ordering (e.g. before manifesto_commit or export_final), and no note on when a check result should block downstream work. Usage must be inferred entirely from the word 'Check'.

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