Conduit Agentic Commerce

Report an issue

agent_report_issue

Report unexpected tool errors or confusing Conduit outcomes for AX review (agent_report_issue — not order_feedback). Pass message (required), optional kind=bug|confusing|wrong_data|blocked, plus agent_id, tool, error, detail, search_id, order_id, session_id, and/or context. Dedupes open reports with the same tool+error+correlation. Does not change reputation.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Triage kind (default confusing): bug \| confusing \| wrong_data \| blocked
`tool`	No	MCP tool that failed or confused you, e.g. supply_search or order_execute
`error`	No	Error code from the prior tool response when present, e.g. offer_not_in_cache
`detail`	No	Optional longer detail (response excerpt, unexpected field). Do not include private_key.
`context`	No	Optional structured extras (args summary, badge, etc.). Secrets are stripped.
`message`	Yes	Required: what went wrong or what confused you (expected vs actual). Keep actionable. This is agent_report_issue — not order_feedback.
`agent_id`	No	Agent id from credentials when available (omit placeholders like "agent_id")
`order_id`	No	order_id for correlation when the issue is order-related
`search_id`	No	search_id for correlation when the issue is search-related
`session_id`	No	Optional session id; Conduit also picks up x-conduit-session-id from the transport
`session_token`	No	Session token from agent_authenticate — required whenever agent_id is passed

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`kind`	No
`next`	No
`tool`	No
`error`	No
`detail`	No
`status`	No
`agent_id`	No
`report_id`	No
`session_id`	No
`already_open`	No
`reported_error`	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 10, 2026
- addedOutput schema / properties / reported_error
```
Added 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

A4.5/5.0

Behavior4/5

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

With all annotations false, the description carries the transparency burden and adds meaningful behaviors: open reports are deduped by tool+error+correlation, and the action 'Does not change reputation.' It does not fully describe every persistence or notification side effect, but the key consequences relevant to an agent are disclosed.

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 dense sentences: purpose and distinction first, parameter guidance second, behavioral caveats last. Every sentence earns its place and the most selection-critical information is front-loaded.

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 an 11-parameter tool with a fully documented schema and an output schema available, the prose plus schema covers required input, optional correlation fields, dedupe behavior, and side-effect-free reputation. Any parameter omitted from the prose (e.g., session_token) is fully specified in the schema, so nothing needed for correct invocation 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 coverage is 100%, and the schema already gives detailed per-parameter descriptions, including 'Do not include private_key' and the session_token requirement. The description mostly restates requiredness and the kind enum; the dedupe sentence adds slight meaning by explaining why tool, error, and correlation fields matter, but no per-parameter detail beyond the schema.

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 begins with a specific action and target: 'Report unexpected tool errors or confusing Conduit outcomes for AX review.' It also explicitly separates itself from the nearest sibling with '(agent_report_issue — not order_feedback),' so an agent can disambiguate without inspecting 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?

It states the trigger conditions ('unexpected tool errors or confusing Conduit outcomes'), names the alternative it is not ('not order_feedback'), and notes the required message plus optional correlation fields. This is explicit when/when-not guidance for selecting the tool.

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?