Skip to main content
Glama

MadMax Trade Supply parts

Create checkout link

create_checkout_link
Read-onlyIdempotent

Build a pre-filled madmaxsupply.com cart link for the buyer. Does NOT place an order or charge anything: the buyer opens the link, enters the address and pays on Stripe-hosted checkout. Optional auto_ship_months (1, 2, 3, 6 or 12) sets up Subscribe & auto-ship on eligible items.

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": {
      "items": "<items>"
    },
    "name": "create_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
ship_to_zipNoOptional 5-digit ship-to ZIP; some regions add a shipping surcharge at checkout.
ship_to_stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ship_to_zip
      Added value: +{
      +  "description": "Optional 5-digit ship-to ZIP; some regions add a shipping surcharge at checkout.",
      +  "type": "string"
      +}
  2. 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 and idempotentHint, but the description adds substantive context: no charge occurs, payment happens on Stripe-hosted checkout after the buyer enters an address, and auto-ship is only applied to eligible items. Gaps remain around link expiry/reuse and what the returned link looks like, so it stops short of full disclosure.

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?

Three tight sentences, front-loaded with the action, then the non-obvious negative constraint, then the optional subscription parameter. Nothing is wasted, though the auto_ship sentence could have carried the full enum including 0 at no extra length cost.

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

Completeness3/5

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

With no output schema, the description bears responsibility for describing the return value, yet it only implies "a link" without stating whether the response is a bare URL, an object, or includes a cart summary or pricing. Combined with the undocumented ship_to_* parameters and the 25-item limit, an agent could call this correctly but not interpret the result confidently.

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 only 33%, and the description compensates partially by explaining what auto_ship_months does and listing allowed values — though it omits 0 (the schema's "no auto-ship" default), which is exactly the value an agent most needs to understand. It says nothing about ship_to_zip, ship_to_state, quantity, or the 25-item cap, leaving meaningful gaps against a low-coverage 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?

"Build a pre-filled madmaxsupply.com cart link for the buyer" names a specific verb (build), resource (cart link), and target store, and is immediately distinguishable from siblings like get_product or check_fit. The opening imperative tells an agent exactly what artifact the call produces.

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 clearly frames the scenario: the buyer wants to complete a purchase and the agent should hand off a pre-filled cart. The explicit "Does NOT place an order or charge anything" delineates the boundary against any order-placement expectation, though it never names an alternative tool or states prerequisites such as when items must be resolved first.

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