Skip to main content
Glama
slide-anki-mcp
by 2Mesh

check_cards

Verifies that each flashcard's answer appears in an exact quote from its cited slide, returning slide text for cards that fail so the quote can be corrected.

Instructions

Check each card {front, back, slide, evidence} against the text of its slide.

'evidence' must be a quote of at least 4 words copied exactly from the cited slide, and 'back' must be inside that quote. Symbols, signs and numbers must match exactly. A passing card means the quote is on the slide. It does not mean the card is correct: read the evidence next to the answer. A failing card comes back with the slide text so the quote can be fixed.

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": {
      "pdf_path": "<pdf_path>",
      "cards": "<cards>"
    },
    "name": "check_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsYes
pdf_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a good job: it explains the exact evidence-matching rules, what a pass actually guarantees, and that a failing card returns slide text for correction. It does not explicitly state permissions, side effects, or that the operation is read-only, which leaves a small gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and then adds only the constraints and interpretation needed to use the result correctly. Every sentence carries useful information, with no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 structure need not be explained, and the description covers validation semantics and failure behavior well. It falls short on pdf_path meaning and explicit read-only/non-mutating assurance, which are relevant for a tool with no annotations.

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 0%, so the description must compensate. It richly defines the card object fields and evidence constraints, but it never explains the required pdf_path parameter or how slides are identified, leaving part of the input semantics undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: checking each card against the text of its cited slide, and names the card fields involved. An agent can immediately tell this is a validation tool rather than an export or slide-retrieval tool like the listed 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 description implies when the tool is useful by explaining passing and failing cards and the evidence rule, but it does not explicitly say when to use this tool versus alternatives or when not to use it. The usage context is clear enough to infer, but no routing guidance is provided.

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