Skip to main content
Glama

CyberNative public PDF accessibility check

Estimate the price to make public PDFs accessible

quote_fix
Read-onlyIdempotent

For one to five links to PDFs on public websites, checks whether each file qualifies and returns a price estimate from CyberNative AI LLC's published Terms for the same PDF with tags added: USD 4 per page, minimum USD 100 per order. Names each file that does not qualify, such as a scanned file, a fillable form, a map or drawing, or a file over 35 pages, with the reason, and does not price it. The estimate is not binding and nothing is ordered by calling this tool; the price is confirmed by email before any work. Use when the user asks what it would cost to have these PDFs made accessible.

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": {
      "urls": "<urls>"
    },
    "name": "quote_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesOne to five links to PDFs on public websites: http or https, at most 2,048 characters each.
detailNoWhen true, adds the page-by-page price for each file that qualifies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / detail / description
      Previous value: -"When true, adds the page-by-page count for each file."New value: +"When true, adds the page-by-page price for each file that qualifies."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description discloses the pricing formula, the disqualification categories (scanned file, fillable form, map or drawing, over 35 pages), that non-qualifying files are named with a reason and not priced, and that the estimate is non-binding with email confirmation. That is exactly the behavioral context annotations cannot convey.

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?

The pricing and eligibility rules are front-loaded in the first clause, and the trigger condition is placed last where it belongs. The opening sentence is long and clause-heavy, bundling qualification rules, exclusions, and disclaimers together, which slightly hurts scannability.

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 no output schema, the description must describe the return value, and it does: a price estimate plus a named list of non-qualifying files with reasons. Combined with the non-binding disclaimer and the eligibility rules, an agent has everything needed to call this correctly and set user expectations.

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 coverage is 100%, so both parameters are already documented, and the description adds little parameter-level meaning beyond restating the one-to-five link limit and the pricing rules. The detail flag's page-by-page expansion is not explained in the description at all. Baseline 3 is appropriate when the schema carries the semantics.

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 states a specific verb and resource: it checks whether one to five public PDF links qualify and returns a price estimate at USD 4/page with a USD 100 minimum. The combined check-plus-price purpose is clear, but the sibling check_public_pdf is never named, so the agent must infer the split between a pure qualification check and this priced estimate.

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?

'Use when the user asks what it would cost to have these PDFs made accessible' gives an explicit trigger condition, and the non-binding / confirmed-by-email caveat sets expectations about what the call does not commit to. There is no explicit when-not guidance or named alternative for callers who only want a pass/fail qualification check.

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