4OVER4

Get the link to cancel a 4OVER4 order

get_order_cancel_link

Read-onlyIdempotent

Gives the link where a customer cancels their own 4OVER4 print order; use it when someone asks to cancel an order. This tool cancels nothing: the customer cancels a job that can still be cancelled on their 4OVER4 orders page, signed in there. To read an order's stage use get_order_details. The order or job number is optional and only names the order in the result. Returns the orders page link. Customer phrases: "cancel order 602074", "I changed my mind on my flyers".

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_order_cancel_link"
  }
}

Input Schema

Name	Required	Description	Default
`jobId`	No	The order or job number the customer wants to cancel, e.g. 602074.

Output Schema

Name	Required	Description
`data`	No	status "cancel_on_4over4", the order number when given, and the customer's orders page on 4over4.com, where the customer cancels a job that can still be cancelled.
`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.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false), so the description adds value by disclosing what the annotations cannot: the tool itself performs no cancellation, and the customer must complete the cancellation while signed in on their orders page. It also pre-empts the expectation of a server-side state change, which is the key behavioral risk here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The most important fact, that this tool cancels nothing, is placed immediately after the purpose statement, and the alternative tool and example phrasings follow in descending order of importance. Every sentence carries distinct information: purpose, negative scope, alternative, parameter caveat, return value, and matching phrases.

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 single optional parameter read-only tool with an output schema, the definition is fully sufficient: purpose, when to use, what it does not do, the routing alternative, the identifier's optional role, and the nature of the return are all covered. The output schema handles return-value detail, so nothing needed for correct invocation 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%, so the parameter's type and example are already documented. The description still adds meaning the schema does not: the job number is optional and serves only to name the order in the result, telling an agent it can safely call this tool without any identifier.

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 states a specific verb and resource: it returns the link where a customer cancels their own 4OVER4 print order. It also draws a sharp line against the sibling get_order_details ("To read an order's stage use get_order_details") and negates the most likely misreading with "This tool cancels nothing."

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 an explicit triggering condition ("use it when someone asks to cancel an order"), names the alternative tool for a related need, and supplies concrete customer phrasings ("cancel order 602074", "I changed my mind on my flyers") that let an agent match real utterances. Nothing about when to select this versus other order tools 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?