4OVER4 Custom Printing

4OVER4 quantity price breaks

price_breaks

Read-onlyIdempotent

Shows every quantity tier and price per piece for one 4OVER4 print product; use it when someone asks how the price changes with quantity or wants bulk pricing. For one exact configuration use configure_product. Requires the product slug. Returns each tier's total and per-piece price for the standard configuration and the best-value tier; size-priced products have no table. Customer phrases: "price breaks on postcards", "how much cheaper if I order 2500", "bulk pricing for flyers".

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": {
      "productSlug": "<productSlug>"
    },
    "name": "price_breaks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Most tiers to return. Default 10.
`productSlug`	Yes	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	Every quantity tier with total and price per piece, and the best-value tier.
`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 this a safe, read-only, idempotent lookup, so the description's job is to add context, which it does: it explains that tiers reflect the standard configuration, that a best-value tier is highlighted, and that size-priced products have no table at all. That caveat is genuinely useful and not derivable from annotations, though pagination or behavior when a slug is unknown is not covered.

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 and the alternative-tool routing are front-loaded in the first two clauses, with caveats after. The trailing list of customer phrases is mildly redundant with the usage sentence but still serves retrieval matching.

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 two-parameter read-only lookup with an output schema and full annotation coverage, the description covers the purpose, the trigger, the alternative, and the important edge case (size-priced products). Nothing an agent needs to call 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 coverage is 100%, so both productSlug and limit are already documented in the schema, and the description only restates that the slug is required. It adds no meaning about how limit interacts with the returned best-value tier, 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 names a specific verb and resource: it 'shows every quantity tier and price per piece for one 4OVER4 print product'. It also explicitly separates itself from configure_product, so an agent can tell the two apart without inspecting 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 conditions directly ('when someone asks how the price changes with quantity or wants bulk pricing') and names the alternative tool with the condition that selects it ('For one exact configuration use configure_product'). The quoted customer phrases reinforce the routing decision.

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

All 4OVER4 Custom Printing 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?