4OVER4

4OVER4 print bleed calculator

calculate_print_bleed

Read-onlyIdempotent

Calculates the full file size with bleed and the safe area for a 4OVER4 print at a trim size; use it when someone asks how much bleed a print file needs. For what bleed means use search_knowledge; for a product's complete setup use get_print_file_setup. Requires trim width and height in inches; bleed defaults to 0.125 inches per side and DPI to 300. Returns the file size in inches and pixels and the safe area. Customer phrases: "how much bleed for 3.5x2 cards".

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_bleed"
  }
}

Input Schema

Name	Required	Description
`dpi`	No	Resolution in dots per inch. Default 300.
`bleedIn`	No	Bleed per side in inches. Default 0.125.
`widthIn`	Yes	Trim width in inches, e.g. 3.5.
`heightIn`	Yes	Trim height in inches, e.g. 2.

Output Schema

Name	Required	Description
`data`	No	The full file size with bleed and the safe-area inset.
`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.5/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds useful context beyond that by stating required trim dimensions, default bleed and DPI values, and what the calculation returns, though it does not elaborate on edge cases such as invalid inputs.

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?

The description is front-loaded with the core purpose and then efficiently covers alternatives, required inputs, defaults, return values, and a customer phrase example. Every sentence contributes to selecting or invoking the tool correctly.

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?

Given that the tool has an output schema, rich annotations, and full schema description coverage, the description provides everything an agent needs: purpose, usage guidance, alternatives, required parameters, defaults, and return summary. No important selection or invocation detail 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 four parameters are already documented in the schema, including defaults and units. The description reinforces that width and height are required in inches and restates the default bleed and DPI, but adds little meaning beyond what the schema already provides.

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 uses a specific verb and resource: it calculates full file size with bleed and safe area for a 4OVER4 print at a trim size. It also distinguishes itself from search_knowledge for bleed definitions and get_print_file_setup for complete product setup, so an agent can route correctly without opening schemas.

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 explicitly says when to use it: when someone asks how much bleed a print file needs. It also names two alternatives and their appropriate conditions, which removes ambiguity for an agent choosing among sibling tools.

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?