Skip to main content
Glama

createCheckout

Create a PayPal Checkout order in USD and return the hosted PayPal approve URL. productId accepts id OR slug. Optional shipToCountry for soft shipping estimate (finalized on PayPal). NO cart. Display: MCP App Pay here → host card → messageToHuman. Wait ~60s then poll getOrderStatus every 60s. Prefer quickCheckout when the human only named a device.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "createCheckout"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoProduct slug — alias for productId
quantityNo
productIdNoProduct id or slug (required unless slug is set)
shipToCountryNoISO country for soft shipping estimate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / shipToCountry
      Added value: +{
      +  "description": "ISO country for soft shipping estimate",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses currency (USD), the returned approve URL, that the shipping estimate is soft and finalized on PayPal, that no cart is involved, and the polling cadence after creation. It stops short of permissions/auth requirements, order expiry or idempotency behavior, which matters for a creation tool.

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?

Dense but front-loaded and short, with the core action, return value, and alternative all in the first lines. The arrow notation for the display flow ("MCP App Pay here → host card → messageToHuman") is cryptic and costs clarity, but nothing is padded.

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 four-parameter creation tool with no annotations and no output schema, it covers the essentials: action, currency, return value, post-call polling loop, and the sibling alternative. Gaps remain around quantity semantics, failure modes, and whether repeated calls create duplicate orders.

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 75%, so the schema already documents productId, slug, and shipToCountry; the description largely restates these (id OR slug, soft shipping estimate). quantity is undocumented in both places, and no syntax, range, or default guidance is added.

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?

Opens with a specific verb and resource — "Create a PayPal Checkout order in USD" — and states the return artifact (hosted PayPal approve URL). It also carves out its territory against quickCheckout, so an agent can pick between the two without opening 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?

Explicitly routes to an alternative with a condition: "Prefer quickCheckout when the human only named a device." It also gives the follow-up path (wait ~60s, then poll getOrderStatus every 60s) and rules out a case with "NO cart", so when-to-use and what-happens-next are both covered.

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