Skip to main content
Glama
sebastienrousseau

inclusio-mcp

by sebastienrousseau
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Audit PDF accessibility (veraPDF)

audit_pdf
Read-onlyIdempotent

Audit built PDFs for PDF/UA-2, WTPDF, and PDF/A-4f accessibility conformance with veraPDF. Returns a detailed report with failures and blocking issues.

Instructions

Audit built PDFs for accessibility conformance with veraPDF.

    Use this to check whether a rendered PDF meets PDF/UA-2, WTPDF, and
    PDF/A-4f before publishing; it shells out to ``verapdf`` read-only
    and never modifies the PDF or the manifest. To produce a document's
    source first call ``render``; to see which documents exist call
    ``list_docs``. This inspects existing PDFs only — it does not build
    them.

    Args:
        target: PDF path or directory. Defaults to `build/` under
            INCLUSIO_CONTENT_DIR.
        strict: When True, every blocking-flavour FAIL is surfaced
            in the response (`blocking_failure: True`); the caller
            decides whether to treat this as an error.

    Returns the audit report dict (summary, by_pdf, by_flavour).
    Requires `verapdf` on PATH; the report contains
    `verapdf_present: False` when it is not.

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

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnly and idempotent. Description adds important context: shells out to verapdf read-only, never modifies PDF/manifest, requires 'verapdf' on PATH, and includes 'verapdf_present' field in response. No contradiction.

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?

Well-structured with clear first sentence, usage paragraph, parameter descriptions, and return info. No redundant or extraneous content; every sentence adds value.

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?

With output schema present, description sufficiently covers return type. Also documents external dependency and failure flag, making it complete for a tool that shells out.

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 covers both parameters fully. Description adds value for 'strict' parameter by explaining caller decides error handling, which enhances semantic clarity beyond 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?

Description clearly states verb 'audit' and specific resource 'built PDFs for accessibility conformance with veraPDF' with explicit standards. Distinguishes from siblings by referencing 'render' and 'list_docs' for related tasks.

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 (before publishing) and what it does not do (does not build or modify). References alternative tools ('render' for production, 'list_docs' for listing) for proper workflow.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/inclusio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server