4OVER4

Find 4OVER4 print products

show_products

Read-onlyIdempotent

Finds 4OVER4 custom print products (business cards, flyers, postcards, banners, stickers, labels, packaging and more) by words, category, budget or goal; use it when someone asks what 4OVER4 has for a print need. For a price use configure_product; for a goal with no product use recommend. All inputs are optional. Returns products with slug, name, From price, rating, 4OVER4's own photo (image_url) and page (url); use those photos, not pictures from other sites. Customer phrases: "soft touch business cards", "cheapest flyers", "signs for a real estate office".

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": "show_products"
  }
}

Input Schema

Name	Required	Description
`qty`	No	Number of printed pieces, e.g. 500.
`sort`	No	Result order: most reviewed, lowest From price, highest rated or newest.
`angle`	No	Industry, occasion, finish, material or shape paired with productType, e.g. wedding.
`limit`	No	Most products to return.
`query`	No	Free words: an industry, occasion, finish, material, shape or product, e.g. "die cut stickers".
`category`	No	Category slug, e.g. business-cards, postcards, flyers.
`maxTotal`	No	Budget for the whole order in USD. An estimate that ignores volume discounts.
`productType`	No	Product type paired with angle, e.g. postcards.

Output Schema

Name	Required	Description
`data`	No	A product grid: slug, name, From price, rating, review count, product link.
`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 establish that this is a read-only, idempotent, non-destructive search. The description adds valuable context about optional inputs, returned fields, and the requirement to use 4OVER4's own image_url rather than third-party photos. It does not discuss pagination beyond the limit parameter, but the output schema covers return shape.

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 purpose and routing guidance, then covers return values and examples. It is slightly long, but every section earns its place by helping an agent choose the right tool and use results 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 eight optional parameters, a fully documented schema, annotations, and an output schema, this description is complete enough to call the tool correctly. It explains routing, input optionality, returned fields, and photo-usage constraints without needing to restate the schema.

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%, so the schema already defines all eight parameters. The description still adds interpretive value by explaining that inputs are optional and by giving customer-style examples such as 'cheapest flyers' and 'signs for a real estate office' that show how query, category, and budget map to real requests.

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: finds 4OVER4 custom print products, with concrete examples of product types. It clearly distinguishes itself from sibling tools by naming configure_product for pricing and recommend for goal-only requests.

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 gives explicit when-to-use guidance: when someone asks what 4OVER4 has for a print need. It also names alternatives and the conditions that select them, including price requests and goal-only requests with no product.

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?