Skip to main content
Glama

Prepare buyer-reviewed commerce

nexez_prepare_commerce
Read-only

Prepare a first-party buyer review page for one exact published offer and checkout or negotiation intent. Reads published facts and checks standard checkout with a forced dry run. The buyer must review and explicitly submit on the hosted page; this tool never submits terms, creates checkout, holds inventory, or pays. Terms and pricing are reviewed again on the page.

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>",
      "intent": "<intent>"
    },
    "name": "nexez_prepare_commerce"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesExact published listing slug returned by discovery, not a URL.
offerYesExact published offer key returned by discovery, for example services-0.
intentYesBuyer-requested action to review on the hosted page: checkout or negotiation.
variantNoCheckout only: exact buyer-selected variant id from product.variants. Required when variants are published.
quantityNoCheckout only: buyer-selected product units. Omit for one unit; respect the published stock and per-order limit.
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.
deliveryPostalCodeNoCheckout only: buyer-provided delivery ZIP for local delivery validation. Never guessed or placed in the review URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

With readOnlyHint=true and destructiveHint=false already declared, the description goes well beyond them: it enumerates the negative space ('never submits terms, creates checkout, holds inventory, or pays'), discloses the forced dry-run behavior, and states that the buyer must explicitly review and submit on the hosted page. It also flags that shipping data is shared 'only with buyer permission for this validation' and warns never to invent or embed an address in the review URL — exactly the kind of operational context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with what the tool does followed by the guarantees and the dry-run detail; no filler. It is dense — several negative guarantees packed into one sentence — but every clause carries information an agent needs.

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 7-parameter tool with a nested address object and no output schema, the description covers side effects, safety guarantees, and the human-in-the-loop handoff, which is the critical unknown. The one gap is what the call actually yields (presumably a hosted review URL, only hinted at by 'placed in the review URL'), which an agent would benefit from knowing explicitly.

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 parameter descriptions are already strong (exact slug not a URL, variant required when variants are published, quantity respects published stock). The description adds only the general note that terms and pricing are reviewed again on the page, which does not clarify any individual parameter. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource: 'Prepare a first-party buyer review page for one exact published offer and checkout or negotiation intent,' plus the secondary action of running a forced dry-run checkout check. The scope ('one exact published offer') is precise. It does not, however, differentiate itself by name from plausible siblings like nexez_validate_checkout or nexez_validate_negotiation, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool is for preparing a hosted buyer review page when checkout or negotiation intent exists, and the buyer must submit there. There is no explicit 'use this when X, use the validate_* tools when Y' routing, and no stated prerequisites (e.g., that slug and offer must first come from discovery). Adequate but leaves the agent to infer selection against siblings.

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