Plain Freight

Track an existing shipment

track_shipment

Read-onlyIdempotent

Reads a booked Plain Freight shipment from its tracking link. Input: the tracking link from the booking email (https://plainfreight.com/track/) or the bare token; the token is the credential, so only someone the customer shared the link with can read the record. Returns the shipment reference, the current stage on the 10-stage lifecycle (Booking through Delivered), shipment details and the dated event log. Read-only; changes to a booking go by email to info@plainfreight.com with the shipment reference.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tracking_link`	Yes	The tracking URL from the booking email (https://plainfreight.com/track/<token>), or the token by itself

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`goods`	No
`stage`	No	e.g. '7 of 10'; null when cancelled
`events`	No
`status`	No
`carrier`	No	Shown only once the invoice is paid
`contact`	No
`lifecycle`	No
`reference`	No
`weight_kg`	No
`record_url`	No
`updated_at`	No
`origin_city`	No
`status_label`	No
`tracking_number`	No	Shown only once the invoice is paid
`destination_city`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "carrier": {
+      "description": "Shown only once the invoice is paid",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "contact": {
+      "type": "string"
+    },
+    "destination_city": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "type": "string"
+    },
+    "events": {
+      "items": {
+        "properties": {
+          "customer_note": {
+            "type": "string"
+          },
+          "happened_at": {
+            "type": "string"
+          },
+          "status": {
+            "description": "Lifecycle status the event belongs to",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "goods": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "lifecycle": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "origin_city": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "record_url": {
+      "type": "string"
+    },
+    "reference": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "stage": {
+      "description": "e.g. '7 of 10'; null when cancelled",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": "string"
+    },
+    "status_label": {
+      "type": "string"
+    },
+    "tracking_number": {
+      "description": "Shown only once the invoice is paid",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "weight_kg": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavioral context by explaining that the token itself is the credential (access is limited to whoever holds the link) and that booking changes must go via email. It does repeat the read-only claim, which is redundant 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.

Conciseness4/5

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

Two dense sentences, front-loaded with purpose and input, then output, then the mutation caveat. Every sentence carries information, though listing the returned fields partially duplicates the output schema.

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 one-parameter read tool with full schema coverage, annotations, and an output schema, the description covers everything an agent needs: input form, access semantics, and the escalation path for changes. Nothing material 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 single parameter's format (full URL or bare token) is already documented in the schema. The description adds the meaningful nuance that the token is the credential, but the schema does the substantive documentation work, so the baseline of 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 (reads/retrieves) and resource (a booked Plain Freight shipment via its tracking link), plus the exact scope of what's returned (reference, lifecycle stage, details, event log). It is clearly distinguishable from siblings like check_offer_status or estimate_price, which operate on offers/pricing rather than an existing shipment record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage context: the tool is for an already-booked shipment and the input comes from the booking email tracking link. It also names the alternative channel for mutations (email info@ with the reference), which implicitly tells the agent this tool is read-only and not the path for changes. It stops short of explicitly contrasting with the sibling lookup tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Plain Freight 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.