Skip to main content
Glama
sebastienrousseau

inclusio-mcp

by sebastienrousseau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Audit PDF accessibility (veraPDF)

audit_pdf
Read-onlyIdempotent

Audits built PDFs for accessibility conformance with veraPDF, verifying PDF/UA-2, WTPDF, and PDF/A-4f compliance. Use before publication to validate regulatory requirements like EAA and WCAG 2.2 AA.

Instructions

Audit built PDFs for accessibility conformance with veraPDF.

    Purpose:
    Verifies whether built PDFs satisfy PDF/UA-2, WTPDF, and PDF/A-4f triple-conformance
    accessibility and preservation standards using veraPDF.

    When to use:
    - When validating accessibility compliance of compiled PDF documents prior to publication.
    - When auditing batch PDFs under `build/` for regulatory standards (EAA, WCAG 2.2 AA).

    When NOT to use:
    - Do NOT use to generate or compile documents; use `render` and the build pipeline first.
    - Do NOT use if veraPDF is not installed or available on PATH.

    Behavioral transparency:
    Read-only audit. Shells out to veraPDF without modifying any PDF or source files.

    Returns:
    Audit report dictionary detailing summary, per-PDF results, and per-flavour passes/fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
strictNoWhen true, every blocking-flavour FAIL is surfaced as `blocking_failure: true` in the response.
targetNoPDF file path or directory to audit; defaults to `build/` under INCLUSIO_CONTENT_DIR.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.0.9
    • addedInput schema / properties / strict / description
      Added value: +"When true, every blocking-flavour FAIL is surfaced as `blocking_failure: true` in the response."
    • addedInput schema / properties / target / description
      Added value: +"PDF file path or directory to audit; defaults to `build/` under INCLUSIO_CONTENT_DIR."
  2. First observedv0.0.7

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: it shells out to veraPDF, modifies no PDF or source files, and fails without veraPDF installed. It does not cover rate/cost or failure semantics of a missing binary.

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 one-line summary followed by clearly labelled sections; every block (purpose, when/when-not, behavior, returns) earns its place. The labelled formatting is slightly heavier than needed but not wasteful.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, fully-annotated tool with an output schema, the description covers purpose, routing, prerequisite, and side-effect profile. The 'Returns' block is supplementary since an output schema exists, and nothing an agent needs to invoke it correctly is missing.

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 100%, so both `strict` and `target` are already documented in the schema; the baseline is 3. The description only echoes the default `build/` directory via the batch-audit example and adds no syntax or format detail beyond the schema.

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?

States a specific verb (audit) and resource (built PDFs) plus the exact standards verified (PDF/UA-2, WTPDF, PDF/A-4f) and the engine (veraPDF). It is clearly distinguishable from siblings like render, which compiles documents rather than auditing them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'When to use' and 'When NOT to use' sections, names the alternative tool (`render` plus the build pipeline) and states a real prerequisite (veraPDF on PATH). Nothing about tool selection is left to inference.

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