4OVER4

4OVER4 print resolution calculator

calculate_print_resolution

Read-onlyIdempotent

Calculates the pixels an image needs for a 4OVER4 print at a given size and DPI; use it when someone asks whether an image is large enough to print. For bleed use calculate_print_bleed; for one product's full file setup use get_print_file_setup. Requires width and height in inches; DPI defaults to 300. Returns the pixel width and height. Customer phrases: "what pixel size for a 4x6 at 300 DPI", "is 1024x768 enough for a 5x7 print".

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": {
      "widthIn": "<widthIn>",
      "heightIn": "<heightIn>"
    },
    "name": "calculate_print_resolution"
  }
}

Input Schema

Name	Required	Description
`dpi`	No	Resolution in dots per inch. Default 300.
`widthIn`	Yes	Width in inches, e.g. 3.5.
`heightIn`	Yes	Height in inches, e.g. 2.

Output Schema

Name	Required	Description
`data`	No	The pixels needed for the size and DPI.
`link`	No	The page on www.4over4.com to continue on: order, upload and checkout happen there.
`summary`	Yes	The facts of the result in plain sentences.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is covered. The description adds meaningful context beyond those: required inch units, the DPI default of 300, and the fact that the result is a pixel width and height. It stops short of describing any edge-case behavior (for example, how rounding or DPI clamping at 36-2400 is handled), so this is strong but not exhaustive.

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 definition is front-loaded with the core behavior, then routing, then requirements. The trailing customer-phrase examples take space but serve a real purpose by anchoring natural-language intent matching; overall it is efficient.

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 a rich annotation set, 100% schema coverage, and an output schema, this description needs only to cover purpose, routing, and input units, all of which it does. An agent has everything required to select and invoke the tool 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 schema already documents each parameter, its units, and the 300 DPI default. The description repeats rather than extends that meaning, adding no new syntax, format, or constraint detail, 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?

The description gives a specific verb and resource: it calculates the pixel dimensions an image needs for a 4OVER4 print at a given size and DPI. It also states the core question it answers ('whether an image is large enough to print'), which distinguishes it from the bleed and file-setup siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use the tool (image-size questions) and explicitly names the alternatives: calculate_print_bleed for bleed and get_print_file_setup for a full product setup. The routing decision is therefore clear without needing to inspect sibling schemas.

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

All 4OVER4 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.

Resources

Need Help?