Skip to main content
Glama
Sign In

PDFLean

by com.pdflean.mcp
OverviewDiscussionsAdmin

Validate PDF/A compliance

pdf_validate_pdfa
Read-onlyIdempotent

Validate a PDF against the PDF/A standard (PDFBox Preflight engine) and return the detailed compliance report. Use this when the user asks whether a PDF is PDF/A-compliant or why it fails PDF/A validation.

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": {
      "file": "<file>"
    },
    "name": "pdf_validate_pdfa"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesBase64-encoded file bytes (no data: URL prefix).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so safety is covered. The description adds useful context beyond that: it identifies the PDFBox Preflight engine and that the result is a detailed compliance report rather than a boolean.

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 tight sentences: the first states the action and return, the second states the trigger. No redundancy or filler; the purpose is front-loaded.

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?

No output schema exists, but the description indicates a detailed compliance report is returned, which is enough orientation for a single-parameter validation tool. Slightly less complete without any hint of the report's structure or size.

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?

Only one parameter, and the schema description covers it at 100% (base64 bytes, no data URL prefix, size limits). The description adds nothing about the file parameter, so the schema carries the load and baseline 3 applies.

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 (Validate), resource (a PDF), and standard (PDF/A), plus the underlying engine. It is clearly distinguishable from the sibling pdf_check_accessibility, which concerns a different standard.

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

Usage Guidelines4/5

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

Explicitly names the trigger conditions: the user asking whether a PDF is PDF/A-compliant or why it fails. It gives clear context for use but does not name an alternative tool or state when not to use it.

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

All PDFLean toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources