Skip to main content
Glama
ARADIA-systems

aradia-mcp-server

Official
by ARADIA-systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

track_order_status

Read-only

Monitor real-time fulfillment, QA burn-in, and delivery status of an existing hardware procurement order using its order ID.

Instructions

[PURPOSE]: Tracks the real-time fulfillment, staging QA burn-in, and delivery status of an active hardware procurement order. [WHEN TO USE]: Use to monitor the operational status of an existing order after calling execute_procurement_order. [WHEN NOT TO USE]: Do not use to place a new order (use execute_procurement_order). [SIDE EFFECTS & BEHAVIOR]: Pure read-only query against staging records. Non-destructive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesThe invoice ID or checkout session ID returned when the order was placed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNoHardware tier.
statusYesCurrent fulfillment state: pending, verified, staging_qa, shipped.
order_idYesOrder identifier.
staging_phaseNoCurrent physical staging phase in the lab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / order_id / description
      Added value: +"The invoice ID or checkout session ID returned when the order was placed."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "order_id": {
+      "description": "Order identifier.",
+      "type": "string"
+    },
+    "staging_phase": {
+      "description": "Current physical staging phase in the lab.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Current fulfillment state: pending, verified, staging_qa, shipped.",
+      "type": "string"
+    },
+    "tier": {
+      "description": "Hardware tier.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "order_id",
+    "status"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the 'pure read-only, non-destructive' line largely restates structured data. It does add that the query runs against staging records, which is useful context, but adds no detail on latency, refresh cadence, or failure modes for an order that isn't found.

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?

The labeled sections front-load purpose and routing, and every clause carries information except the trailing 'Non-destructive', which duplicates the annotations. Bracketed labels add scanability at a small token cost.

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?

An output schema exists so return values need no explanation, annotations carry the safety profile, and the description covers purpose, routing, and data source. Nothing an agent needs to invoke this 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% and the single order_id parameter is fully documented in the schema (invoice ID or checkout session ID). The description adds nothing beyond that, so the baseline 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 (tracks) and resource (fulfillment/QA/delivery status of a hardware procurement order), and explicitly separates itself from the sibling execute_procurement_order. An agent can distinguish it from execute_procurement_order and query_hardware_specs 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?

Provides explicit WHEN TO USE (monitor an existing order after execute_procurement_order) and WHEN NOT TO USE (do not place a new order) with the named alternative. There is no ambiguity about routing.

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

Deploy Server

Other Tools