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
`tracking_source`	No
`merchant_observed`	No
`handoff_expires_at`	No
`agent_status_locked`	No

Schema Changelog

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

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 meaningful behavioral guarantees beyond the annotations: 'never fabricates carrier scans' discloses that the tool returns real tracking data and does not generate placeholder information. It also highlights the authorization requirement ('Requires owning agent_id'), which is not fully covered by the readOnlyHint annotation. This provides useful transparency about the tool's behavior.

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 a single, concise sentence that avoids unnecessary verbosity. However, phrases like 'deal-type-aware' are somewhat cryptic and could be more explicit without adding length. Overall, it is well-structured and easy to parse.

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?

Given that an output schema exists, the description does not need to explain return values. However, it lacks clarity on what 'deal-type-aware status' means and what specific tracking information is provided. The mention of 'never fabricates carrier scans' gives some context, but the overall domain context is thin, making it less complete for an agent deciding to call this tool.

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?

The schema already provides descriptions for all parameters (agent_id, order_id, session_token) with 100% coverage, so the baseline is 3. The description adds a slight semantic enhancement by emphasizing that agent_id must be the owning agent, but it does not clarify the purpose or format of order_id or session_token beyond the schema's existing descriptions.

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 'Honest deal-type-aware status' which suggests retrieving tracking status but is vague and does not explicitly state the action (e.g., 'retrieve tracking information for an order'). It does not clearly distinguish from sibling tools like order_events or order_list, which could also provide status-related information.

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?

No guidance is provided on when to use this tool versus alternatives. The only instruction is 'Requires owning agent_id,' which is a prerequisite, not a usage comparison. There is no mention of scenarios where order_track should be preferred over order_events or other order-related tools.

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

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.

Resources

Need Help?