EasyAccessPDF

eap_check_pdf

Read-onlyIdempotent

Check a PDF for accessibility compliance (PDF/UA-1, ISO 14289-1) using veraPDF. Included with membership — no credits charged. Returns pages, grade (A/B/C/F), issue list, tag coverage. Pass a publicly accessible URL of the PDF.

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": {
      "url": "<url>"
    },
    "name": "eap_check_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Publicly accessible URL of the PDF (max 50MB)

Output Schema

Name	Required	Description	Default
`pages`	Yes
`issues`	No
`has_tags`	No
`included`	No
`validator`	No
`pass_grade`	Yes
`credits_charged`	No
`tag_coverage_pct`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered; the description adds genuinely new context about what comes back (pages, A/B/C/F grade, issue list, tag coverage) and reinforces that the tool fetches over the network, requiring public reachability. It does not mention failure modes for unreachable or non-compliant files, keeping it below a 5.

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?

Four short sentences, purpose front-loaded, with no filler. The ordering is slightly scattered, placing the URL requirement last after cost and return details, but nothing is wasted.

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 single-parameter read-only tool with full schema coverage, annotations and an output schema, this is essentially complete. The enumeration of return fields is mildly redundant given the output schema, but no information an agent needs to call it 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?

There is only one parameter and schema description coverage is 100%, with the 50MB limit documented in the schema itself. The description's 'publicly accessible URL' phrasing restates rather than extends that schema meaning, so the baseline of 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?

Names a specific verb (check), resource (PDF), the exact compliance standard (PDF/UA-1, ISO 14289-1), and the engine (veraPDF). This is unambiguous and clearly distinct from siblings like eap_fix_pdf and eap_export_pdf, which act on the PDF rather than evaluating it.

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?

Gives clear invocation context: pass a publicly accessible URL, and notes it is free for members (no credits), which is a real selection factor versus other tools. It stops short of explicitly routing the agent between this and eap_fix_pdf (check-then-fix), so it is not a full when/when-not statement.

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

All EasyAccessPDF tools Inspect

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.