Skip to main content
Glama

Check an Anki deck

check_deck
Read-onlyIdempotent

Check if an Anki deck exists with a case-insensitive name match and return its exact name for accurate quiz or card setup.

Instructions

Check whether a deck exists. Matching ignores letter case, and the result gives the exact deck name. Read-only.

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": "<deck>"
    },
    "name": "check_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYesName of an Anki deck. Matched without regard to letter case.

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the 'Read-only' sentence adds little. The description does add real behavior beyond annotations: matching is case-insensitive and the response returns the canonical deck name, which matters because there is no output schema.

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 purpose front-loaded and no filler. The trailing 'Read-only' duplicates the annotations and is the only wasted clause.

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 simple single-parameter tool with annotations covering safety, this is nearly sufficient, and it usefully mentions the returned canonical name. It omits the negative case — whether a non-existent deck yields false or an error — which is exactly the outcome an agent must handle.

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 coverage is 100% and the single 'deck' parameter already documents case-insensitive matching and length bounds. The description restates the case-insensitivity but contributes no additional meaning beyond the schema, so the baseline 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 ('Check whether a deck exists') so an agent can distinguish an existence probe from listing or exporting decks. It does not explicitly name a sibling tool to contrast with, which keeps it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The existence-check framing implies when to reach for it (validating a deck name before another operation), but there is no explicit when-to-use, when-not-to-use, or named alternative such as list_decks. Guidance is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.