Conduit Agentic Commerce

Update order status

order_update_status

Agent manual correction or degraded handoff recovery. note required except cancelled. Owning agent_id required.

Input Schema

TableJSON Schema

Name	Required	Description
`note`	No	Required note except when status=CANCELLED
`status`	Yes	New status, e.g. PENDING, CONFIRMED, SHIPPED, DELIVERED, CANCELLED
`carrier`	No	Carrier name when attaching tracking
`agent_id`	Yes	Owning agent id (required for authorization)
`order_id`	Yes	Order id to update
`search_id`	No	Optional search_id for analytics correlation
`tracking_id`	No	Carrier tracking id when recovering handoff
`tracking_url`	No	Carrier's public tracking page for tracking_id, when you have it. Never invent one.
`session_token`	No	Session token from agent_authenticate — required whenever agent_id is passed
`handoff_endpoint`	No	Merchant handoff/status endpoint URL for poll recovery
`external_checkout_id`	No	Merchant checkout id to recover degraded handoff polling

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`next`	No
`error`	No
`detail`	No
`status`	No
`carrier`	No
`order_id`	No
`quantity`	No
`tracking_id`	No
`continue_url`	No
`handoff_endpoint`	No
`merchant_observed`	No
`agent_status_locked`	No
`external_checkout_id`	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"
```

Changed1 schema field changedSep 14, 2026

addedInput schema / properties / tracking_url

Added value: +{
+  "description": "Carrier's public tracking page for tracking_id, when you have it. Never invent one.",
+  "format": "uri",
+  "type": "string"
+}

Changed14 schema fields changedAug 29, 2026
- removedOutput schema / properties / agentStatusLocked
```
Removed value: -{
-  "type": "boolean"
-}
```
- addedOutput schema / properties / agent_status_locked
```
Added value: +{
+  "type": "boolean"
+}
```
- removedOutput schema / properties / continueUrl
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / continue_url
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / externalCheckoutId
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / external_checkout_id
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / handoffEndpoint
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / handoff_endpoint
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / merchantObserved
```
Removed value: -{}
```
- addedOutput schema / properties / merchant_observed
```
Added value: +{}
```
- 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.4/5.0

Behavior3/5

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

Annotations already indicate a mutating, non-idempotent, non-destructive operation with open-world semantics. The description adds useful context about the tool's purpose and the authorization requirement ('Owning agent_id required'), but does not disclose potential side effects, idempotency implications, or validation behavior beyond the note condition. This is adequate but not rich.

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 compact and every sentence earns its place, covering the two use cases and two critical operational constraints. It is somewhat terse and could be better front-loaded with the primary purpose, but there is no filler or redundancy.

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?

For a complex 11-parameter, non-idempotent mutation tool, the description is minimal. It conveys the main scenarios and key requirements, but gives no workflow guidance for degraded handoff recovery, no mention of session_token even though it is conditionally required, and no indication of how optional tracking/handoff parameters relate. The schema and output schema compensate, but the description alone leaves meaningful gaps.

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 schema already documents all 11 parameters. The description reinforces two critical constraints—note required except cancelled and owning agent_id required—but adds little beyond that. This matches the baseline of 3 for fully covered schemas.

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

Purpose4/5

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

The name and title clearly identify the action and resource: updating an order's status. The description adds two specific use contexts—manual correction and degraded handoff recovery—which help distinguish it from read-style siblings like order_track and order_events. It does not explicitly contrast a sibling, but the resource and verb are unambiguous.

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?

The description states when to use the tool: for agent manual correction or recovery from a degraded handoff. It also highlights key preconditions such as 'note required except cancelled' and 'Owning agent_id required'. However, it does not explicitly say when not to use it or name alternatives, leaving some routing inference to the agent.

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?