Plain Freight

Check an offer's second review

check_offer_status

Read-onlyIdempotent

Reads the result of the second check on a Plain Freight offer, by the offer's quote_id. Read-only. Returns settled (true once the check finished), possibly updated options and summary, follow-up questions whose answers change the price or customs channel, the offer email status, and needs_review. When needs_review is true, prices are withheld until a person at Plain Freight reviews the goods (for example batteries, food or chemicals), and Plain Freight follows up by email.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`quote_id`	Yes	The quote_id of a Plain Freight offer (a UUID)

Output Schema

TableJSON Schema

Name	Required	Description
`text`	No
`email`	No	Offer email status: sent, queued, deferred, skipped or failed
`error`	No
`options`	No
`settled`	No
`quote_id`	No
`questions`	No
`needs_review`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / quote_id / description

Previous value: -"The quote_id returned by generate_offer"New value: +"The quote_id of a Plain Freight offer (a UUID)"

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "email": {
+      "description": "Offer email status: sent, queued, deferred, skipped or failed",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "type": "string"
+    },
+    "needs_review": {
+      "type": "boolean"
+    },
+    "options": {
+      "items": {
+        "properties": {
+          "duties_included": {
+            "description": "true when US import duty is inside the price (DDP); false when duty is paid to the government at import",
+            "type": "boolean"
+          },
+          "firm": {
+            "description": "false means an estimate confirmed before booking",
+            "type": "boolean"
+          },
+          "includes": {
+            "description": "Exactly what this price covers",
+            "type": "string"
+          },
+          "key": {
+            "description": "air, sea or express",
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "price": {
+            "description": "Price in USD for the whole shipment",
+            "type": "number"
+          },
+          "transit": {
+            "description": "Door to door transit estimate",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "questions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "quote_id": {
+      "type": "string"
+    },
+    "settled": {
+      "type": "boolean"
+    },
+    "text": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the 'settled' flag flips true only once the check finishes, prices are withheld when needs_review is true (batteries, food, chemicals), and follow-up happens by email. These are workflow behaviors the agent could not infer from 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?

Single paragraph, front-loaded with purpose and read-only status, then the return semantics. Sentences are information-dense with no filler, though the enumeration of return fields is somewhat list-like. Slightly long but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not detail return shapes, yet it still explains the meaning of settled and needs_review and the withheld-price path. Annotations cover safety. Combined with a single well-documented required param, this is close to complete; only explicit usage/preconditions are 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?

Only one parameter (quote_id) with 100% schema description coverage stating it is a UUID of a Plain Freight offer. The description repeats 'by the offer's quote_id' without adding format, sourcing, or error semantics. Baseline 3 applies when the schema carries the parameter documentation.

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?

Specific verb + resource + scope: 'Reads the result of the second check on a Plain Freight offer, by the offer's quote_id.' It clearly identifies which stage of the offer lifecycle this covers, distinguishing it from siblings like generate_offer and estimate_price. An agent can select it 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 Guidelines3/5

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

Usage is implied (poll the second check's result, keyed by quote_id) but never stated explicitly, and no alternative or precondition is named. It does not say, for example, that this should be called after generate_offer, or what to do before an offer exists. Adequate but with clear gaps.

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.