Nexez Agentic Commerce

Validate Nexez checkout

nexez_validate_checkout

Read-only

Dry-run checkout for an exact published offer. Returns validation JSON text with offer readiness or errors and missing requirements. Inspect the offer with nexez_get_page first. Never charges or creates an order; a successful check is not a completed purchase.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Exact published listing slug returned by discovery, not a full URL.
`offer`	Yes	Exact offer key from the listing manifest, for example services-0 or products-1. Do not invent an index.
`query`	No	Optional buyer context
`buyerEmail`	No	Optional buyer-provided email for checkout context. Omit when unnecessary; never invent personal details.
`buyerReference`	No	Optional buyer-provided reference for checkout context; omit if none was supplied.
`offerConfiguration`	No	Buyer-selected configuration values keyed exactly as defined by the target offer configuration schema from nexez_get_page. Supply required fields for that offer; do not invent values or use a generic schema.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 8, 2026

addedInput schema / properties / buyerEmail / description

Added value: +"Optional buyer-provided email for checkout context. Omit when unnecessary; never invent personal details."

addedInput schema / properties / buyerReference / description

Added value: +"Optional buyer-provided reference for checkout context; omit if none was supplied."

changedInput schema / properties / offer / description

Previous value: -"e.g. services-0 or products-1"New value: +"Exact offer key from the listing manifest, for example services-0 or products-1. Do not invent an index."

changedInput schema / properties / offerConfiguration / description

Previous value: -"Canonical buyer values required by the target offer configuration schema."New value: +"Buyer-selected configuration values keyed exactly as defined by the target offer configuration schema from nexez_get_page. Supply required fields for that offer; do not invent values or use a generic schema."

addedInput schema / properties / slug / description

Added value: +"Exact published listing slug returned by discovery, not a full URL."

Changed3 schema fields changedAug 21, 2026

addedInput schema / properties / buyerEmail
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / buyerReference
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / offerConfiguration

Added value: +{
+  "description": "Canonical buyer values required by the target offer configuration schema.",
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the readOnlyHint=true and destructiveHint=false annotations: 'Never charges or creates an order; a successful check is not a completed purchase.' It also discloses the nature of the return value, which is valuable since no output schema is present.

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 three concise sentences with no filler. It front-loads the core purpose and return value, then adds the prerequisite and the critical non-charge guarantee. Every sentence earns its place.

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?

The description is complete for a dry-run validation tool: it explains purpose, output shape, prerequisites, and the safety guarantee. Despite having no output schema, it clearly states what the agent will receive in response. The detailed input schema covers parameter semantics, so nothing critical 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 input schema already fully documents all six parameters. The description adds no parameter-specific detail, but the schema provides clear guidance such as 'not a full URL' and 'Do not invent an index,' making this baseline 3 appropriate.

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 states a specific action ('Dry-run checkout') and a specific resource ('an exact published offer'), and clarifies the return value ('validation JSON text with offer readiness or errors and missing requirements'). This clearly distinguishes it from sibling tools like nexez_get_page or nexez_validate_negotiation.

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 explicitly instructs the agent to inspect the offer with nexez_get_page first, establishing a clear prerequisite. It also clarifies when not to interpret a successful result as a completed purchase, though it does not explicitly contrast this with nexez_validate_negotiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nexez 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?