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. For most catalog offers the payload equals the object supply_search already returned, so skip this if you still hold that offer and only need its fields. 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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`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
`price_total`	No
`payment_rails`	No
`payment_terms`	No
`delivery_options`	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 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.7/5.0

Behavior5/5

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

The description adds rich behavioral context beyond the annotations: it reads from a cache, refreshes badge/action against mandate state, carries no shipping data, and exposes a specific error condition (offer_not_in_cache). This is fully consistent with the readOnly, idempotent, and non-destructive hints, and it tells the agent what to expect in terms of side-effects (none) and failure modes.

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

Conciseness5/5

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

Three sentences, front-loaded with the core purpose, then immediate alternatives and an error condition. Every sentence earns its place; there is no filler or redundancy. The structure leads with what the tool does, then tells the agent when to skip it and what to use instead.

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?

Given the output schema exists, the description does not need to explain return values. It covers the tool's purpose, usage guidelines, behavioral nuances, error handling, and exclusions, leaving no gap an agent would need to infer. For a tool with four parameters and one required, this is complete and self-sufficient.

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 coverage is 100%, so all four parameters are already documented with clear descriptions. The description does not add additional semantic meaning beyond what the schema provides; it only reinforces the purpose of each parameter without new details. A baseline score of 3 is appropriate when the schema already carries the full parameter documentation.

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?

The description clearly states a specific verb ('re-reads'/'refreshes') and resource ('one offer from the search cache'), and distinguishes itself from siblings like supply_search and supply_delivery. It tells the agent exactly what this tool does and what it doesn't do, making it unambiguous even without opening the schema.

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?

It provides explicit when-to-use and when-not-to-use guidance: skip if you already hold the offer, use supply_delivery for shipping data, and re-run supply_search on offer_not_in_cache. These are concrete, actionable conditions that route the agent to the correct tool in every scenario.

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?