4OVER4

My 4OVER4 orders

get_my_orders

Read-onlyIdempotent

Lists the signed-in customer's 4OVER4 print orders with their stage; use it when someone asks about their own orders. For one known order number use get_order_details. Inputs are optional: status and search narrow the list, insights adds totals. Returns order number, date, product, total and stage, newest first; with insights, spend and order totals. Needs the customer's 4OVER4 sign-in. Customer phrases: "what is my order status", "my postcard orders", "how much did I spend this year".

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

Input Schema

Name	Required	Description
`limit`	No	Most orders to return. Default 10.
`search`	No	Product name or order number.
`status`	No	Stage filter, e.g. delivered, shipped, in production, cancelled.
`insights`	No	true adds order count, total spend, coins earned and top products.

Output Schema

Name	Required	Description
`data`	No	The customer's orders: order number, date, product, total, stage; with insights, totals.
`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?

Beyond the readOnly/idempotent annotations, it discloses the auth requirement ("Needs the customer's 4OVER4 sign-in"), the sort order (newest first), and what changes when insights is set. It does not discuss empty results or the limit ceiling beyond the schema, so it falls just short of fully self-contained.

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?

Dense but front-loaded: purpose and the sibling routing come first, and the trailing customer-phrase list is functional rather than filler. A few clauses (return fields, auth) are packed into a single run-on sentence, costing some scannability.

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 read-only list tool with an output schema and fully documented parameters, this covers purpose, auth, filtering, sorting, and the insights mode. 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 description coverage is 100%, so the schema already documents limit, search, status, and insights. The description restates their effect in prose ("status and search narrow the list, insights adds totals") but adds no syntax, format, or edge-case detail beyond what the schema supplies. Baseline 3 is appropriate.

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?

"Lists the signed-in customer's 4OVER4 print orders with their stage" gives a specific verb, resource, and scope. It also explicitly contrasts with get_order_details for single-order lookups, so the agent can route correctly without opening either 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?

States when to use it ("when someone asks about their own orders") and names the alternative for the adjacent case ("For one known order number use get_order_details"). It even maps customer phrasings to the tool, which removes ambiguity for intent matching.

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?