Skip to main content
Glama
Sign In

massprint

by com.themassprint
OverviewDiscussionsAdmin

PDF upload report

validate_pdf
Read-onlyIdempotent

Get the report for an uploaded PDF: page count, page size, the size its pages are or are scaled to (by_sku[sku].page_fit, e.g. A4 at 10×), and warnings. The report is advice: no file is refused for its content, and our print team checks every file against the order after payment. The one exception is a storybook, whose page count sets the price: create_order refuses a count we do not price (page_count_out_of_range). Free to call. Reads only your own uploads: without an API key, the uploads you made without one; with a key, that key's uploads.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "validate_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYesThe upload_id returned by create_upload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations, it discloses that the report is advisory, no file is refused for content, storybook page counts can cause create_order refusal, calls are free, and upload visibility depends on API-key scope. These are meaningful behavioral details not covered by the structured fields.

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 description is front-loaded with the report purpose and return fields, and each sentence contributes useful context. It is somewhat dense in a single paragraph but not padded.

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?

For a read-only report tool with one documented parameter and no output schema, the description covers return fields, advisory behavior, the storybook pricing exception, cost, and access scoping. An agent has enough context to call it correctly.

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%, and the only parameter is already documented as the upload_id returned by create_upload. The description adds no parameter-level meaning beyond that baseline.

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?

The description states a specific verb and resource: get the report for an uploaded PDF. It lists the report contents and distinguishes relevant behavior from create_order, especially the storybook pricing exception.

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?

It gives clear usage context: the report is advisory, the print team checks files later, and storybook page counts affect create_order. It does not explicitly say when to call this instead of other siblings or state exclusions, so it falls short of full alternative routing.

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

All massprint 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