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

list_slides

Lists every slide in a lecture PDF with its first line and text length, flagging low-text slides that cannot be used to verify generated Anki cards.

Instructions

List every slide in a lecture PDF (full path) with its first line and text length.

A slide with a 'warning' has little or no text. Cards cannot be checked against it.

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

Input Schema

NameRequiredDescriptionDefault
pdf_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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 behavioral burden. It does disclose one non-obvious trait — the 'warning' flag meaning a slide has little or no text and is unusable for card checking — but says nothing about error behavior for a bad path, whether parsing is expensive, or ordering of results. Output schema exists, so return shape need not be explained.

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?

Two short sentences, purpose front-loaded, no wasted wording. The second sentence is slightly muddy — 'it' has no clear antecedent, leaving the warning-slide rule usable only after inference.

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?

For a one-parameter read tool with an output schema already documenting return values, the description covers the essential purpose and the one surprising data trait (warning slides). The only meaningful gap is routing guidance relative to get_slide and check_cards.

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% and the schema itself only says 'Pdf Path', so the description must compensate. '(full path)' does add a genuine constraint beyond the schema, but format details such as absolute vs relative paths or file-extension expectations are still left ambiguous for the single required parameter.

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 names a specific verb and resource ('List every slide in a lecture PDF') and states exactly what each item carries (first line and text length). That is enough to distinguish it from 'get_slide' (single slide) and 'check_cards', though it never explicitly contrasts 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?

Usage is only implied: you call it to survey a PDF's slides before doing card work. The line 'Cards cannot be checked against it' hints at a downstream constraint but does not say when to prefer this over get_slide or how it fits into a check_cards workflow. No explicit when/when-not guidance is 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