Skip to main content
Glama

verify_slides

Run programmatic slide checks to detect overlapping or out-of-bounds shapes, empty text, tiny shapes, unused placeholders, layout drift, and background covers, returning a list of issues.

Instructions

Run programmatic checks on a slide: detect overlapping shapes, out-of-bounds shapes, empty text, tiny shapes, unused placeholders, placeholder drift from layout defaults, and full-bleed background covers. Returns a list of issues found. Uses the same shape data as inspect_slide — no OOXML needed.

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

Input Schema

NameRequiredDescriptionDefault
slideYesSlide number, 1-based (slide 1 = first slide)
checksNoChecks to run. Default: all checks.
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • addedInput schema / properties / slide
      Added value: +{
      +  "description": "Slide number, 1-based (slide 1 = first slide)",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based slide index",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slideIndex"
      -]New value: +[
      +  "slide"
      +]
  2. First observedv0.6.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does reasonably well: it states that the tool returns a list of issues, names each detection category, and discloses the data source so the agent knows no OOXML parsing or external tooling is involved. It stops short of explicitly stating that the operation is read-only and does not modify the slide, and it does not describe the issue record shape or severity, which is the remaining gap.

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?

The description is front-loaded with the core action and keeps the long check list compact in one sentence; every clause is functional. The list is dense but earns its space because the enum names alone are not self-explanatory.

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 bounded, read-oriented verification tool with fully documented parameters, this is nearly complete: it says what is checked, what is returned, and where the data comes from. The missing piece is the structure of an issue record, which matters because no output schema exists to document it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning by expanding the cryptic enum values into human-readable checks (e.g. "layout_drift" becomes "placeholder drift from layout defaults"). It adds nothing for the slide number or presentationId parameters, but those are self-explanatory in the schema.

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?

"Run programmatic checks on a slide" gives a clear verb and resource, and the enumeration of the seven checks makes the scope concrete and distinguishable from a general inspector. It also names inspect_slide as the data-equivalent sibling, though it does not contrast itself with scan_slide, which appears to be the nearest overlapping alternative.

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 sentence "Uses the same shape data as inspect_slide — no OOXML needed" implies a relationship and suggests verify_slides is the diagnostic layer over the same data. However, there is no explicit when-to-use, when-not-to-use, or guidance on choosing between verify_slides, scan_slide, and inspect_slide, leaving the routing decision to inference.

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