Skip to main content
Glama

check

Free preflight: checks a PDF against a product's print requirements and returns previews with issues marked. Creates no order and needs no address or payment; the file is stored for the check.

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": {
      "pdf": "<pdf>",
      "product": "<product>"
    },
    "name": "check"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdfYesThe print-ready PDF, as an https URL it can be downloaded from (at most 32 MB), or the id (fil_…) of a file sent before.
foldNoFilter by fold.
sizeNoFilter by size.
sidesNoFilter by sides.
stockNoFilter by stock.
finishNoFilter by finish.
optionNoFilter by any option, as key=value. Repeatable.
productYesProduct id or alias, e.g. flyer.
all_issuesNoReturn every issue instead of up to 3 per code.
orientationNoFilter by orientation.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

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?

Goes beyond the annotations by disclosing cost (free), the absence of ordering side-effects, that no address or payment is required, and that the uploaded file is retained for the check — which usefully explains why readOnlyHint is false despite the read-like framing. It does not cover auth requirements, retention duration, or rate/size handling beyond the schema's 32 MB note.

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?

A single tight sentence pair with the value proposition ('Free preflight') front-loaded, followed by the scope-limiting facts. Nothing is redundant and nothing competes for attention.

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?

With an output schema covering the returned previews and annotations covering the safety profile, the description only needed to add cost, side-effects, and file handling — all of which are present. Minor gaps remain around file retention and what happens on repeated checks, but nothing critical to calling it correctly 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?

Schema description coverage is 100%, so all ten parameters, including the pdf URL/file-id forms and the filter fields, are already documented. The description adds no meaning about how the fold/size/sides/stock/finish/orientation filters interact with product resolution, 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?

States a specific verb and resource: checks a PDF against a product's print requirements and returns previews with issues marked. The clause 'Creates no order' actively distinguishes it from the order_* siblings, so an agent can route correctly without opening the schema.

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?

Frames the tool as a 'Free preflight', which implies when to reach for it, and the note that it creates no order and needs no address or payment clarifies the boundary against order_create/order_quote. It stops short of explicitly naming a sibling or stating a when-not condition, so it falls just under the top band.

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