Conduit Agentic Commerce

What to reorder

inventory_replenishment

Read-onlyIdempotent

Items below their minimum in your own system, least days of cover first, with what is already inbound and the usual vendor and last price. Each row carries a search_hint: pass its query and quantity straight to supply_search, then supply_availability before ordering. Optional location scopes to one warehouse. Needs inventory permission.

Input Schema

TableJSON Schema

Name	Required	Description
`fresh`	No	Ask the system now instead of reading the last value
`agent_id`	Yes	Agent id; its organization owns the connected system
`location`	No	Warehouse or store name to scope the worklist, e.g. "Jebel Ali". Omit for all
`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
`rows`	No
`as_of`	No
`basis`	No
`error`	No
`detail`	No
`system`	No
`window`	No
`freshness`	No
`provenance`	No
`connections`	No
`connection_id`	No
`next_to_watch`	No
`could_not_reach`	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.5/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds meaningful behavioral context: the rows are sorted 'least days of cover first', each row carries a search_hint contract, location can scope the result, and inventory permission is required. This goes well beyond the structured 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?

Three sentences with no wasted words. Core output is front-loaded, followed by the downstream action and scope/permission details. Every sentence carries essential information.

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?

For a read-only reporting tool with an output schema and safety annotations, the description covers output content, sort order, downstream workflow, location scoping, and permissions. Nothing an agent needs to select and invoke it correctly 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%, and the description does not materially add to parameter meaning beyond restating that location is optional and scopes to a warehouse. The baseline 3 is appropriate because the schema already documents all five parameters.

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?

Description clearly defines the tool's output as items below minimum stock sorted by days of cover, with inbound quantities, vendor, and last price. The title 'What to reorder' reinforces this, and the content distinguishes it from sibling tools like inventory_levels and supply_search by positioning it as the replenishment worklist with search hints for downstream sourcing.

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?

Description gives explicit operational flow: 'pass its query and quantity straight to supply_search, then supply_availability before ordering.' It also states location scoping and the permission requirement. It does not explicitly name alternatives or when not to use the tool, so it misses the 'when-not' clause, but the workflow guidance is strong.

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?