SCVD General Store

Check an Order

check_order

Read-onlyIdempotent

Check a human-queue order by its order_id: status (queued or completed), the promised window, and once completed the deliverable itself — the poll half of the store's async-job pattern, the same record GET /api/order/{order_id} serves, for an agent holding only this transport. Free, no payment, no account; poll no faster than once a minute. Past its window the order carries a window_breached block stating what is owed. NOT a purchase; instant items arrive in the buy result. A store errand, for you the visiting agent — nothing here needs a human's decision.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_id`	Yes	The order_id from a human-queue purchase result.

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Where the order stands. Completed is terminal.
`item_id`	Yes	What was bought.
`message`	Yes	The store's word on where things stand.
`order_id`	Yes	The order polled.
`badge_url`	No	The patron badge, an SVG.
`item_name`	No	Its name on the shelf.
`sla_hours`	Yes	The delivery promise, in hours from created_at.
`created_at`	Yes	When the order was taken, ISO 8601.
`deliverable`	No	The goods, as text. Present once status is completed.
`completed_at`	No	When it was delivered, ISO 8601. Present once completed.
`patron_number`	No	Your sequential patron number.
`window_breached`	No	Present only past the promised window. The store counting a missed promise against itself, in full.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed5 schema fields changedSep 6, 2026

changedOutput schema / properties / status / description

Previous value: -"queued | completed. Completed is terminal."New value: +"Where the order stands. Completed is terminal."

addedOutput schema / properties / status / enum

Added value: +[
+  "queued",
+  "completed"
+]

changedOutput schema / properties / window_breached / description

Previous value: -"Present only past the promised window: due_at, hours_late, kind, owed_usdc, and how the refund gets paid (by the keeper's hand, never automatically)."New value: +"Present only past the promised window. The store counting a missed promise against itself, in full."

addedOutput schema / properties / window_breached / properties

Added value: +{
+  "due_at": {
+    "description": "When the window closed, ISO 8601.",
+    "type": "string"
+  },
+  "hours_late": {
+    "description": "How far past it, in hours.",
+    "type": "number"
+  },
+  "how_it_gets_paid": {
+    "description": "That the keeper pays refunds by hand, with a transaction hash on the record.",
+    "type": "string"
+  },
+  "kind": {
+    "description": "Whether it arrived late or has still not arrived.",
+    "enum": [
+      "delivered_late",
+      "still_open"
+    ],
+    "type": "string"
+  },
+  "note": {
+    "description": "What the promise says about this case, in plain words.",
+    "type": "string"
+  },
+  "owed_usdc": {
+    "description": "What is owed back, in USDC.",
+    "type": "number"
+  },
+  "verify": {
+    "description": "The order's own URL, for checking this independently.",
+    "type": "string"
+  }
+}

addedOutput schema / properties / window_breached / required

Added value: +[
+  "due_at",
+  "hours_late",
+  "kind",
+  "owed_usdc"
+]

First observedSep 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: statuses are queued/completed, it returns the promised window and deliverable, a window_breached block appears when past the window, and it is free with no account. It also clarifies the operation is a read-only polling pattern consistent with the readOnlyHint. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is dense but every sentence carries distinct information: core purpose, transport context, polling cadence, free/no-auth, window breach behavior, and purchase exclusion. It front-loads the primary function before adding caveats, and no sentence is wasted.

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?

Given the single fully-documented parameter, present annotations, and an output schema, the description covers all the operational context an agent needs. It explains the polling rate, the breached-window payload, the purchase boundary, and the source of order_id. Nothing critical is missing.

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 schema already fully describes order_id with coverage at 100%, so the baseline is 3. The description adds value by clarifying that order_id comes from a human-queue purchase result, which tells the agent where to obtain the value. That extra provenance justifies a 4 rather than the baseline.

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 states a clear verb and resource: check a human-queue order by order_id, reporting status, promised window, and deliverable once completed. It also explicitly distinguishes itself from purchase tools by saying 'NOT a purchase; instant items arrive in the buy result.' This makes it easy to tell apart from sibling tools.

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 says exactly when to use the tool: for an agent holding only this transport to poll the async human-queue job. It gives the polling constraint ('poll no faster than once a minute'), notes that no payment or account is needed, and explicitly excludes purchases, saying instant items arrive in the buy result. This provides clear when-to and when-not-to guidance.

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

All SCVD General Store tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.