4OVER4

4OVER4 delivery date

delivery_by_zip

Read-onlyIdempotent

Gives the in-hands date for one 4OVER4 print product, with an estimate for a US ZIP code when given one; use it when someone asks when their business cards, flyers, banners or other prints would arrive. For a price use configure_product; for shipping methods in general use search_knowledge. Requires the product slug; the ZIP code and quantity are optional. Returns production days, a shipping estimate and the in-hands date. Customer phrases: "when would 500 flyers arrive in 10001", "how fast can I get banners".

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": {
      "slug": "<slug>"
    },
    "name": "delivery_by_zip"
  }
}

Input Schema

Name	Required	Description
`qty`	No	Number of printed pieces, e.g. 500.
`zip`	No	Destination US ZIP code, exactly 5 digits, e.g. 10001.
`slug`	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	Production days, shipping estimate and in-hands date.
`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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: what it returns (production days, shipping estimate, in-hands date) and that a ZIP-less call still yields an estimate rather than failing. It does not mention auth or rate limits, which is a minor gap given the annotations.

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 purpose and the sibling routing are front-loaded, and the trailing customer-phrase examples are genuinely useful for utterance matching. It is slightly overpacked into one long opening sentence, but no clause is wasted.

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 3-parameter read tool with an output schema, annotations and full schema coverage, everything an agent needs is present: inputs, required vs optional, return shape, and alternative tools. Return values are documented even though the output schema already carries them.

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 baseline is 3, but the description adds meaning beyond the schema: slug is required and sourced from product-listing results, while zip and qty are optional and zip only sharpens the estimate. That optionality-to-effect mapping is not obvious from the schema alone.

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?

States a specific verb and resource — returns the in-hands date for a single 4OVER4 print product, optionally ZIP-scoped — and explicitly separates it from configure_product (pricing) and search_knowledge (general shipping methods). An agent can identify it without opening the 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?

Gives an explicit use condition ("use it when someone asks when their business cards, flyers, banners or other prints would arrive") and routes two adjacent needs — price and general shipping info — to named alternatives. Nothing is left to inference.

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?