Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "offer": "<offer>"
    },
    "name": "nexez_validate_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesExact published listing slug returned by discovery, not a full URL.
offerYesExact offer key from the listing manifest, for example services-0 or products-1. Do not invent an index.
queryNoOptional buyer context
variantNoExact variant id from product.variants in nexez_get_page. Required when the product lists variants; do not invent one.
quantityNoUnits to buy for a product offer; defaults to 1. Stay within product.max_per_order and product.stock_count from nexez_get_page.
buyerEmailNoOptional buyer-provided email for checkout context. Omit when unnecessary; never invent personal details.
buyerReferenceNoOptional buyer-provided reference for checkout context; omit if none was supplied.
shippingAddressNoRequired for shipped products: the buyer-provided US address, shared with Nexez only with buyer permission for this validation. Shipping uses product.shipping rates. Never invent an address.
deliveryPostalCodeNoBuyer-provided delivery ZIP for a local delivery product whose product.local_delivery.zips is listed. Omit otherwise.
offerConfigurationNoBuyer-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.

  1. Changed9 schema fields changed
    • addedInput schema / properties / shippingAddress / additionalProperties
      Added value: +false
    • changedInput schema / properties / shippingAddress / description
      Previous value: -"Required for a shipped product (fulfillment \"shipped\"): the buyer-provided US address. Shipping is the flat rate for its region from product.shipping. Never invent an address."New value: +"Required for shipped products: the buyer-provided US address, shared with Nexez only with buyer permission for this validation. Shipping uses product.shipping rates. Never invent an address."
    • addedInput schema / properties / shippingAddress / properties / city / maxLength
      Added value: +100
    • addedInput schema / properties / shippingAddress / properties / line1 / maxLength
      Added value: +200
    • addedInput schema / properties / shippingAddress / properties / line2 / maxLength
      Added value: +200
    • addedInput schema / properties / shippingAddress / properties / name / maxLength
      Added value: +100
    • changedInput schema / properties / shippingAddress / properties / postalCode / description
      Previous value: -"5-digit ZIP."New value: +"5-digit ZIP or ZIP+4."
    • addedInput schema / properties / shippingAddress / properties / postalCode / maxLength
      Added value: +10
    • addedInput schema / properties / shippingAddress / properties / state / maxLength
      Added value: +2
  2. Changed1 schema field changed
    • addedInput schema / properties / shippingAddress
      Added value: +{
      +  "description": "Required for a shipped product (fulfillment \"shipped\"): the buyer-provided US address. Shipping is the flat rate for its region from product.shipping. Never invent an address.",
      +  "properties": {
      +    "city": {
      +      "type": "string"
      +    },
      +    "line1": {
      +      "type": "string"
      +    },
      +    "line2": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "postalCode": {
      +      "description": "5-digit ZIP.",
      +      "type": "string"
      +    },
      +    "state": {
      +      "description": "Two-letter US state code.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "line1",
      +    "city",
      +    "state",
      +    "postalCode"
      +  ],
      +  "type": "object"
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / deliveryPostalCode
      Added value: +{
      +  "description": "Buyer-provided delivery ZIP for a local delivery product whose product.local_delivery.zips is listed. Omit otherwise.",
      +  "type": "string"
      +}
    • addedInput schema / properties / quantity
      Added value: +{
      +  "description": "Units to buy for a product offer; defaults to 1. Stay within product.max_per_order and product.stock_count from nexez_get_page.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / variant
      Added value: +{
      +  "description": "Exact variant id from product.variants in nexez_get_page. Required when the product lists variants; do not invent one.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, yet the description adds genuine context: the call never charges or creates an order, and a passing check is explicitly not a completed purchase — a non-obvious semantic an agent could otherwise misreport. It also states what comes back (validation JSON text with errors and missing requirements), compensating for the absent output schema.

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?

Four short sentences, purpose and return shape front-loaded, then prerequisite, then safety semantics. Each sentence carries distinct information — no filler and no restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with a nested shipping address and no output schema, the description supplies the context an agent needs: ordering relative to nexez_get_page, the nature of the response, and the no-side-effect guarantee. Minor gap: it does not flag that variant is conditionally required or how partial validation failures should be surfaced.

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 each parameter (slug, offer, variant, quantity, shippingAddress, offerConfiguration, deliveryPostalCode, etc.) is already documented with constraints and provenance. The description adds no parameter-level meaning beyond the schema; the baseline 3 applies when the schema does the work.

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?

States a specific verb (dry-run validate) and resource (checkout for an exact published offer), and discloses the return shape (validation JSON with readiness or errors and missing requirements). It distinguishes itself from a real purchase flow by saying it never charges or creates an order, but it does not explicitly contrast with nearby siblings such as nexez_prepare_commerce.

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?

Gives an explicit prerequisite sequence: inspect the offer with nexez_get_page first, before validating. It also implies the when-not case by framing itself as a dry run whose success is not a purchase. It stops short of naming an alternative tool for the cases where validation fails or for actually completing checkout.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources