Conduit Agentic Commerce

Get delivery estimate

supply_delivery

Read-onlyIdempotent

Non-committing checkout probe for shipping ETA/cost. Uses agent default_destination, else linked org default address, or country override. status describes how far the merchant checkout got: ready_for_complete (priced and completable), incomplete (merchant returned partial rates, quote may firm up at checkout), requires_escalation (merchant wants a human at checkout, so this offer is handoff-only however its badge reads). needs_interaction=true means the same. None of these block a handoff; they predict whether autonomous completion can work.

Input Schema

TableJSON Schema

Name	Required	Description
`region`	No	Optional region/state override
`address`	No	Street override. Many merchants will not quote shipping without it.
`country`	No	ISO country override, e.g. US (else agent/org destination)
`agent_id`	No	Agent id — uses agent destination else org default when country omitted
`locality`	No	City override. Needed with street for a real delivery quote.
`quantity`	No	Units to price shipping for (default 1)
`supply_id`	Yes	Offer supply id from supply_search / supply_details
`postal_code`	No	Postal/ZIP override for the probe destination
`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
`note`	No
`error`	No
`detail`	No
`status`	No
`country`	No
`options`	No
`currency`	No
`eta_text`	No
`available`	No
`shippable`	No
`supply_id`	No
`postal_code`	No
`payment_rails`	No
`shipping_cost`	No
`address_status`	No
`needs_interaction`	No
`placeholder_street`	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"
```

Changed4 schema fields changedSep 10, 2026

addedInput schema / properties / address

Added value: +{
+  "description": "Street override. Many merchants will not quote shipping without it.",
+  "type": "string"
+}

addedInput schema / properties / locality

Added value: +{
+  "description": "City override. Needed with street for a real delivery quote.",
+  "type": "string"
+}

addedOutput schema / properties / address_status
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / placeholder_street
```
Added value: +{
+  "type": "boolean"
+}
```

Changed11 schema fields changedAug 29, 2026
- removedOutput schema / properties / etaText
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / eta_text
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / needsInteraction
```
Removed value: -{
-  "type": "boolean"
-}
```
- addedOutput schema / properties / needs_interaction
```
Added value: +{
+  "type": "boolean"
+}
```
- removedOutput schema / properties / paymentRails
```
Removed value: -{}
```
- addedOutput schema / properties / payment_rails
```
Added value: +{}
```
- removedOutput schema / properties / postalCode
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / postal_code
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / shippingCost
```
Removed value: -{
-  "type": "number"
-}
```
- addedOutput schema / properties / shipping_cost
```
Added value: +{
+  "type": "number"
+}
```
- removedOutput schema / properties / supplyId
```
Removed 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

A3.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive; the description adds substantial non-redundant context: the non-committing nature (no order placed), the precise semantics of each status value (ready_for_complete, incomplete, requires_escalation), the destination-resolution chain, and the clarification that needs_interaction=true means the same as requires_escalation. No contradiction with annotations.

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

Conciseness2/5

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

The purpose is front-loaded well, but the body is a single run-on paragraph with tangled clauses ('so this offer is handoff-only however its badge reads', 'needs_interaction=true means the same'). The status enumeration should be structured as a list, and the redundant handoff explanation could be tightened substantially.

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

Completeness4/5

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

An output schema covers return values and rich annotations cover the safety profile, lowering the burden. The description thoroughly covers status semantics and destination resolution for a 9-parameter tool, leaving little functionally missing. The deficiency is organizational, not informational.

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?

Schema coverage is 100%, giving a baseline of 3. The description adds genuine precedence semantics not present in the schema — the ordered destination resolution (agent default_destination, then linked org default, then country override) — which clarifies how agent_id, country, and address parameters interact. This elevates it above baseline.

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?

Opens with a specific verb+resource — 'Non-committing checkout probe for shipping ETA/cost' — which clearly differentiates it from siblings like supply_search, supply_details, supply_options, and supply_availability by framing it as a checkout-level estimate probe rather than a catalog or availability lookup. It stops short of naming a specific alternative to distinguish against, so not a 5.

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?

Provides destination-resolution precedence (agent default → linked org default → country override) and explains how to interpret status outcomes and when autonomous completion can work. However, it never explicitly states when to prefer this over supply_options/supply_availability or when not to use it, leaving routing to inference.

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?