4OVER4

My 4OVER4 cart

get_cart

Read-onlyIdempotent

Shows the signed-in customer's own 4OVER4 print cart; use it when someone asks what is in their cart. It only reads the cart; items are added on www.4over4.com product pages. For past orders use get_my_orders. Takes no input. Returns the cart lines with product, quantity and price, the total and the checkout link on www.4over4.com. Needs the customer's 4OVER4 sign-in. Customer phrases: "what is in my cart", "my cart total", "take me to checkout", "did my business cards stay in my cart".

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`data`	No	Cart lines, total and the checkout link on 4over4.com.
`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 behavior, so the safety profile is covered. The description still adds useful context beyond them: the sign-in prerequisite and the fact that cart mutation happens on www.4over4.com, not through this tool. It stops short of noting anything about empty-cart or session-expiry behavior, which keeps it from a 5.

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?

Purpose, boundary, alternative, input contract, and return shape are front-loaded in that order with no filler sentences. The trailing list of customer phrases is somewhat padded but does real work in mapping colloquial requests to this 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 zero-parameter read tool with an output schema, the description covers everything an agent needs: what it returns (cart lines, total, checkout link), the sign-in requirement, and where mutations must happen instead. Nothing essential is left to inference.

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?

The tool takes no parameters, so the baseline is 4, and the description explicitly confirms "Takes no input," removing any doubt about required identifiers. No further parameter meaning is needed or missing.

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 opens with a specific verb and resource ("Shows the signed-in customer's own 4OVER4 print cart") and scopes it to the caller's own cart, which separates it from order-lookup and product-browsing siblings. An agent can identify the tool's job 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?

It gives an explicit trigger ("use it when someone asks what is in their cart"), names the alternative for a neighboring need ("For past orders use get_my_orders"), and rules out a plausible but wrong use by stating that items are added on the website product pages rather than here.

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?