Conduit Agentic Commerce

Track order

order_track

Read-onlyIdempotent

Honest deal-type-aware status (never fabricates carrier scans). Requires owning agent_id.

Input Schema

TableJSON Schema

Name	Required	Description
`agent_id`	Yes	Owning agent id (required for authorization)
`order_id`	Yes	Order id to track
`session_token`	No	Session token from agent_authenticate — required whenever agent_id is passed

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`next`	No
`error`	No
`detail`	No
`status`	No
`carrier`	No
`product`	No
`order_id`	No
`recovery`	No
`tracking`	No
`trackable`	No
`checkout_id`	No
`tracking_id`	No
`continue_url`	No
`status_source`	No
`address_status`	No
`purchase_draft`	No
`supplier_order`	No
`tracking_source`	No
`merchant_observed`	No
`handoff_expires_at`	No
`agent_status_locked`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026
- addedOutput schema / properties / next / properties / args / additionalProperties / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
```
- removedOutput schema / properties / next / properties / args / additionalProperties / type
```
Removed value: -"string"
```
Changed2 schema fields changedSep 20, 2026
- addedOutput schema / properties / purchase_draft
```
Added value: +{}
```
- addedOutput schema / properties / supplier_order
```
Added value: +{}
```
Changed1 schema field changedSep 7, 2026
- addedOutput schema / properties / address_status
```
Added value: +{
+  "type": "string"
+}
```
Changed6 schema fields changedAug 29, 2026
- removedOutput schema / properties / continueUrl
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / continue_url
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / orderId
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / order_id
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / trackingId
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / tracking_id
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedAug 10, 2026

addedInput schema / properties / session_token

Added value: +{
+  "description": "Session token from agent_authenticate — required whenever agent_id is passed",
+  "type": "string"
+}

AddedJul 26, 2026

TDQS

B3.1/5.0

Behavior4/5

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

The description adds useful behavioral context beyond the annotations: it promises not to fabricate carrier scans and explicitly states the ownership/auth requirement. These details are not present in the readOnlyHint/openWorldHint/idempotentHint annotations, so the description meaningfully supplements them.

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 description is short and free of filler, with the core behavioral promise front-loaded. However, 'deal-type-aware' is a somewhat unclear term that could reduce precision, so it is not quite a perfect 5.

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

Completeness3/5

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

The output schema covers return values and the annotations cover safety, but the description omits usage context relative to sibling tools and does not mention the session_token requirement that appears in the schema. For a tool with an auth-sensitive parameter, this leaves some gaps in call correctness.

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%, so the parameters are already fully documented in the schema. The description only reinforces the agent_id requirement without adding new semantic information about order_id or session_token, so it stays at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'status' and 'never fabricates carrier scans', which implies order tracking, but it never explicitly states that it returns tracking status for a given order. It does not clearly distinguish itself from sibling tools like order_events or order_list, and the phrase 'deal-type-aware' is vague without explanation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as order_events or order_list. The only usage hint is the auth requirement ('Requires owning agent_id'), which is more of a prerequisite than a usage guideline.

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

All Conduit Agentic Commerce 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.

Resources

Need Help?