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

anki-workflow-mcp

by Gugart43
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Validate Hints

validate_hints

Checks cloze hint annotations for synonym overlap, binary alternatives, target root leakage, and empty hints, returning issues to fix before flashcards are published.

Instructions

Validate hints in a cloze sentence '{{cN::target::hint}}'. Checks: HINT.SYNONYM (high overlap), HINT.ELIMINATION (binary alternatives), HINT.ROOT_LEAK (target root in hint), HINT.FORMAT (empty hint).

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": {
      "sentence": "<sentence>"
    },
    "name": "validate_hints"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowNo
sentenceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does partially meet it by naming the four check categories (synonym overlap, binary elimination, root leak, empty hint), which is genuine behavioral detail. However, it never states whether the tool is read-only or modifies the sentence, nor how findings are reported or how severe they are.

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?

Front-loaded with the verb and object, then a compact enumerable checklist of checks – no filler sentences. The code names (HINT.SYNONYM etc.) are dense but efficiently structured for machine consumption.

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 return values need not be spelled out, but for a two-parameter validation tool with zero schema coverage and no annotations the description leaves one parameter undefined and does not state whether the operation is safe/read-only. Adequate, with clear gaps.

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 0%, so the description must compensate: it explains the expected structure of the 'sentence' value, which is useful. The second parameter 'row' (integer, default 0) is never mentioned, and it is unclear whether the sentence is parsed as Anki markup or plain text.

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 (validate) and resource (hints) and pins down the exact syntax being validated: a cloze sentence in the form '{{cN::target::hint}}'. It also enumerates the four check codes, so the agent knows precisely what class of problem is detected; only sibling differentiation (e.g. vs. validate_cloze) is absent.

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 tool name and the notation it validates – an agent can infer it runs on hint fields inside cloze cards. There is no explicit statement of when to run it versus validate_cloze or the batch validators, and no prerequisites or exclusions are given.

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