Skip to main content
Glama

pdf-suite

pdf_compliance_audit

Audit a PDF for hidden 3-Tr invisible text operators, OCG layers, active /JS, annotations, and metadata leaks, and optionally issue a SHA-256 Compliance Certificate PDF.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_compliance_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathNo
filenameNodocument.pdf
base64DataNo
outputPathNoOptional local output path for SHA-256 Compliance Certificate PDF.
generateCertificatePdfNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It does add real behavioral content: the specific audit categories and that the certificate is SHA-256 based and optional. However, it never states whether the audit is read-only or modifies the input PDF, what the findings look like, or where the certificate is written beyond the separate outputPath parameter.

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?

A single front-loaded sentence with no filler; every clause names a distinct audit check or the optional certificate. It is dense and slightly run-on, but nothing is redundant.

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

Completeness2/5

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

A five-parameter tool with no annotations, no output schema, and 20% schema description coverage needs more than one sentence. The description never explains the shape of the audit results, the input-mode choice, or whether the certificate requires generateCertificatePdf plus outputPath, leaving the agent to infer operational details.

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

Parameters2/5

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

Schema description coverage is only 20% (just outputPath), so the description must compensate and largely does not. It implies a certificate-issuance mode tied to generateCertificatePdf, but leaves filePath, filename (default document.pdf), and base64Data unexplained, including the important question of how input is supplied (path vs inline base64) and whether they are alternatives.

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?

The description pairs a specific verb ('Audit') with a specific resource ('a PDF') and enumerates the concrete checks performed: invisible 3-Tr text operators, OCG layers, active /JS, annotations, and metadata leaks. It also states the optional side effect (SHA-256 Compliance Certificate PDF). It doesn't explicitly differentiate from pdf_repair, but 'audit' versus 'repair' is inherently a different intent.

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?

Usage is only implied: you call this when you want a PDF inspected for hidden/embedded risks. There is no statement of when to prefer this over pdf_repair, no prerequisites, and no note on whether the input PDF is left untouched. The word 'optionally' is the only guidance on mode selection, and it maps to a flag rather than a decision scenario.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources