track_guest_orderOrder status, tracking number/URL, shipping method and line items for any order, given the order number and the delivery postcode (no sign-in needed).
| Name | Required | Description | Default |
|---|---|---|---|
| postcode | Yes | Delivery postcode / ZIP on the order. | |
| order_number | Yes | Order number from the confirmation email. |
| Name | Required | Description | Default |
|---|---|---|---|
| order | Yes | ||
| track_url | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "order": {
+ "additionalProperties": false,
+ "properties": {
+ "currency": {
+ "type": "string"
+ },
+ "discount": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "express_promised_dispatch_date": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "is_express": {
+ "type": "boolean"
+ },
+ "items": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "line_total": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "quantity": {
+ "type": "number"
+ },
+ "sku": {
+ "type": "string"
+ },
+ "unit_price": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "sku",
+ "name",
+ "quantity",
+ "unit_price",
+ "line_total"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "order_date": {
+ "type": "string"
+ },
+ "order_number": {
+ "type": "string"
+ },
+ "paid_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "shipped_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "shipping_company": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "shipping_cost": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "shipping_method": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "shipping_to": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "city": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "country_code": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "postal_code": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "city",
+ "postal_code",
+ "country_code"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "status": {
+ "type": "string"
+ },
+ "subtotal": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "tax": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "total": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "tracking_number": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "tracking_url": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "order_number",
+ "status",
+ "order_date",
+ "currency",
+ "total",
+ "subtotal",
+ "shipping_cost",
+ "tax",
+ "discount",
+ "shipping_method",
+ "tracking_number",
+ "tracking_url",
+ "shipping_company",
+ "shipped_at",
+ "paid_at",
+ "items",
+ "shipping_to"
+ ],
+ "type": "object"
+ },
+ "track_url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "order",
+ "track_url"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context: this works for 'any order' with just an order number and postcode, and requires no sign-in, which is important for understanding access and prerequisites. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence: it leads with the returned information and then states the inputs and access requirement. There is no filler, repetition, or unnecessary structuring.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only lookup with two fully documented parameters and an output schema present, the description covers everything an agent needs: what the tool returns, how to identify the order, and that no login is needed. No important context is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and both parameters have clear descriptions in the schema. The tool description references the two inputs but adds no parameter-specific detail beyond what the schema already provides, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is specific: it states that the tool returns order status, tracking number/URL, shipping method, and line items for an order. It also clarifies the identifying inputs (order number and delivery postcode) and adds 'no sign-in needed', which differentiates it from order tools that require authentication or from narrower delivery-status siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly indicates when to use the tool: whenever you need order information via order number plus postcode, with no sign-in required. It does not explicitly name alternative tools or exclusion conditions, but the usage context is clear enough for an agent to select it correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.