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

get_slide

Fetch the exact text of a 1-based slide from a lecture PDF to copy evidence quotes and ground flashcard answers in the source material.

Instructions

Return the exact text of one slide (1-based). Copy evidence quotes from this text.

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

Input Schema

NameRequiredDescriptionDefault
slideYes
pdf_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/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 burden. It does disclose that this is a read of exact text and that slide numbering is 1-based, which is genuinely useful behavioral detail, but it says nothing about permissions, failure behavior for out-of-range slides, or cost. Adequate but with clear gaps for an unannotated tool.

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?

Two short sentences with zero filler; the indexing convention and the intended follow-up action are both front-loaded. Nothing could be removed without losing signal.

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 values need no explanation, and the tool is a simple two-parameter read. The remaining gap is the unelaborated pdf_path argument, the only thing an agent could plausibly get wrong.

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 does add the critical '1-based' convention for the slide index that the bare schema ('Slide': integer) omits. But pdf_path receives no explanation of accepted formats (path vs. URL, relative vs. absolute), so half the parameters remain unexplained.

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?

"Return the exact text of one slide" gives a specific verb (return) and resource (slide text) plus a scope qualifier ('one slide'), which is enough to distinguish it from a listing sibling like list_slides. It stops short of explicitly naming the alternative, so it is clear but not fully differentiated.

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?

"Copy evidence quotes from this text" implies the downstream use case (quoting for evidence/citation), which is useful context. However, there is no explicit when-to-use vs. when-not guidance and no mention of list_slides as the alternative for enumerating slides, leaving usage only implied.

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