Conduit Agentic Commerce

Usual vendors and last prices

inventory_suppliers

Read-onlyIdempotent

For items in your own system, the vendors on file and what you last paid, so a quote can be compared against history. Needs inventory permission. Does not contact any vendor.

Input Schema

TableJSON Schema

Name	Required	Description
`skus`	Yes	Item codes in your own system whose usual vendors and last prices to read
`agent_id`	Yes	Agent id; its organization owns the connected system
`connection_id`	No	Which connected system, when the org has several
`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
`as_of`	No
`basis`	No
`error`	No
`detail`	No
`system`	No
`freshness`	No
`suppliers`	No
`connections`	No
`connection_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"
```
AddedSep 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds value by stating the permission requirement and clarifying that no vendor contact occurs, which is useful behavioral context beyond the annotations.

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?

The description is two tight sentences with no filler. It front-loads the resource and purpose, then states the permission and non-contact behavior, making it easy for an agent to parse quickly.

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 100% schema coverage, rich annotations, and the presence of an output schema, the description supplies the remaining needed context: the use case, permission requirement, and lack of vendor contact. Nothing essential for selecting or invoking the tool is missing.

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 baseline is 3 and the description does not need to re-explain parameters. It reinforces the meaning of 'skus' as items 'in your own system' and adds the historical-price context, but it does not provide significant per-parameter detail beyond the schema.

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 description clearly identifies the resource: on-file vendors and last-paid prices for items in the user's own system, and ties it to a concrete use case (comparing a quote against history). It lacks an explicit verb like 'list' or 'retrieve' and does not name a sibling alternative, though the 'own system' and 'Does not contact any vendor' statements do help distinguish it from external supply tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear context for use ('so a quote can be compared against history') and states a prerequisite ('Needs inventory permission'). It also implies when not to use it by saying it does not contact any vendor, but it does not explicitly name or exclude sibling tools such as supply_search.

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?