Conduit Agentic Commerce

Get supply details

supply_details

Read-onlyIdempotent

Re-reads one offer from the search cache and refreshes its badge/action against current mandate state. Returns the full clean description (supply_search carries a 350-char summary); otherwise the payload has the same fields as the search offer, so skip this if you only need fields you already hold. include_description_original=true adds description_original {format, content}, the merchant's own markup (untrusted), or description_original_omitted with the reason. Carries no shipping data: use supply_delivery for ETA and cost. Re-run supply_search if offer_not_in_cache.

Input Schema

TableJSON Schema

Name	Required	Description
`agent_id`	No	Agent id to refresh badge/action for mandate state
`search_id`	No	search_id from supply_search for correlation
`supply_id`	Yes	Offer supply id from supply_search results
`session_token`	No	Session token from agent_authenticate — required whenever agent_id is passed
`include_description_original`	No	Adds description_original {format, content}: the merchant's own markup, for rendering or checking our conversion. Untrusted merchant text. supply_details only.

Output Schema

TableJSON Schema

Name	Required	Description
`aes`	No
`hint`	No
`next`	No
`badge`	No
`error`	No
`title`	No
`action`	No
`detail`	No
`currency`	No
`supplier`	No
`supply_id`	No
`unit_price`	No
`description`	No
`price_total`	No
`payment_rails`	No
`payment_terms`	No
`delivery_options`	No
`description_original`	No	Only with include_description_original. The merchant's markup, untrusted. format is html or markdown today; plain is reserved.
`description_original_omitted`	No	Only with include_description_original, when there is no original: no_markup (plain text or none), oversize (over 20,000 chars), empty (markup with no visible text).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 13, 2026

addedInput schema / properties / include_description_original

Added value: +{
+  "description": "Adds description_original {format, content}: the merchant's own markup, for rendering or checking our conversion. Untrusted merchant text. supply_details only.",
+  "type": "boolean"
+}

addedOutput schema / properties / description
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / description_original

Added value: +{
+  "additionalProperties": false,
+  "description": "Only with include_description_original. The merchant's markup, untrusted. format is html or markdown today; plain is reserved.",
+  "properties": {
+    "content": {
+      "type": "string"
+    },
+    "format": {
+      "enum": [
+        "html",
+        "markdown",
+        "plain"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "format",
+    "content"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / description_original_omitted

Added value: +{
+  "description": "Only with include_description_original, when there is no original: no_markup (plain text or none), oversize (over 20,000 chars), empty (markup with no visible text).",
+  "enum": [
+    "no_markup",
+    "oversize",
+    "empty"
+  ],
+  "type": "string"
+}

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 3, 2026

addedOutput schema / properties / payment_terms

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed9 schema fields changedAug 29, 2026
- removedOutput schema / properties / deliveryOptions
```
Removed value: -{}
```
- addedOutput schema / properties / delivery_options
```
Added value: +{}
```
- removedOutput schema / properties / paymentRails
```
Removed value: -{}
```
- addedOutput schema / properties / payment_rails
```
Added value: +{}
```
- removedOutput schema / properties / priceTotal
```
Removed value: -{}
```
- addedOutput schema / properties / price_total
```
Added value: +{}
```
- removedOutput schema / properties / supplyId
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / unitPrice
```
Removed value: -{}
```
- addedOutput schema / properties / unit_price
```
Added value: +{}
```

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

A4.8/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds real behavior: re-evaluation against current mandate state, the payload difference vs search results, and that description_original is untrusted merchant markup. It also discloses the error condition and its remedy.

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?

Front-loaded with the core action and scope, then alternatives and caveats. Information-dense but every clause carries signal; only the parenthetical payload comparison is slightly compressed for reading.

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, yet the description still covers the parts an agent needs to choose correctly: when it is redundant, what it adds over search, what it lacks (shipping), and how to recover from a cache miss.

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%, so the baseline is 3, but the description adds meaning beyond the schema by explaining what include_description_original actually yields (description_original {format, content} or description_original_omitted with a reason) and tying agent_id to mandate-state refresh.

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 precise verb and resource — re-reads one offer from the search cache and refreshes its badge/action against mandate state. It explicitly contrasts itself with supply_search (350-char summary vs full description) and supply_delivery, so an agent can distinguish it from siblings without opening schemas.

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?

Gives explicit when-not guidance ('skip this if you only need fields you already hold'), names the alternative for shipping data ('use supply_delivery for ETA and cost'), and prescribes the recovery path ('Re-run supply_search if offer_not_in_cache').

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?