4OVER4

4OVER4 print file setup

get_print_file_setup

Read-onlyIdempotent

Gives the artwork setup for a 4OVER4 print file: size, bleed, safe margin, 300 DPI, CMYK and file formats such as PDF; use it when someone asks how to set up a file for printing. For arithmetic at a custom size use calculate_print_bleed. The product slug is optional: with it the result uses that product's default size, without it the general setup. Customer phrases: "file requirements for business cards", "how do I set up my flyer file".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_print_file_setup"
  }
}

Input Schema

Name	Required	Description	Default
`productSlug`	No	Product slug, from the slug field of a show_products, recommend or find_similar_products result, e.g. standard-business-cards.

Output Schema

Name	Required	Description
`data`	No	One product's file setup, or the general setup.
`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.6/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the bar is lower; the description adds real behavioral context by explaining that presence of the slug switches the result from general setup to that product's default size. It does not describe pagination or response structure, but an output schema exists to cover that.

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 core capability, the alternative tool, and the optional-parameter behavior are front-loaded with no wasted framing. The trailing list of customer phrases is slightly extraneous padding, though it does aid matching against user wording.

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?

A one-optional-parameter read tool with full schema coverage, a complete annotation set, and an output schema. The description supplies purpose, trigger, alternative, and optional-parameter semantics — nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents productSlug and its source, so the baseline is 3. The description earns an extra point by explaining the semantic effect of supplying versus omitting the slug, which the schema itself does not state.

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 names a specific resource and enumerates the returned subject matter: size, bleed, safe margin, 300 DPI, CMYK and file formats such as PDF. It also explicitly distinguishes itself from calculate_print_bleed, so an agent can pick between the two without opening either schema.

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 the triggering condition ("when someone asks how to set up a file for printing") and names the alternative with its own condition ("For arithmetic at a custom size use calculate_print_bleed"). The optional-slug behavior is also framed as two distinct usage cases: with a slug vs. general setup.

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?