4OVER4 Custom Printing

4OVER4 order details, tracking or invoice

get_order_details

Read-onlyIdempotent

Shows one 4OVER4 print order by its number: items, stage, tracking or invoice; use it when someone gives an order number or asks where their prints are. For a list of orders use get_my_orders. Requires the exact order or job number; view selects details, tracking or invoice. Returns the jobs, money, stage timeline, carrier link or invoice. Needs the customer's 4OVER4 sign-in. Customer phrases: "where is order 602074", "track my order", "send me the invoice for 602074".

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": {
      "jobId": "<jobId>"
    },
    "name": "get_order_details"
  }
}

Input Schema

Name	Required	Description	Default
`view`	No	details (default), tracking or invoice.
`jobId`	Yes	The exact order or job number, e.g. 602074 or 602074-03.

Output Schema

Name	Required	Description
`data`	No	One order: its jobs, money, stage timeline, carrier link or invoice.
`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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured context: the customer must be signed in to 4OVER4, and an exact order/job number is mandatory. It stops short of noting failure modes (e.g. what happens with a non-matching number).

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?

Front-loaded with purpose, then alternative routing, then prerequisites and returns. Semicolon-chained and dense but every clause carries routing or usage information; the customer-phrase list is slightly padded but earns its place for a conversational commerce tool.

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 2-parameter read tool with full schema descriptions, annotations and an output schema, the description covers purpose, alternative, required input form, auth prerequisite and return contents. Nothing an agent needs in order 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% and the description largely restates it: 'view selects details, tracking or invoice' mirrors the enum, and 'exact order or job number' repeats the jobId description. The added value is minimal beyond signaling that the number must match exactly, so the baseline 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?

States a specific verb and resource with scope: shows ONE 4OVER4 print order by number, returning items, stage, tracking or invoice. The list-vs-single distinction against get_my_orders is explicit, so an agent can separate the two without inspecting 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?

Gives explicit triggers (someone supplies an order number, asks where their prints are) and an explicit alternative ('For a list of orders use get_my_orders'). The customer-phrase examples ('where is order 602074', 'track my order') make routing unambiguous.

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?