Skip to main content
Glama

quickCheckout

ONE-SHOT: resolve a verified-fit kit and return a hosted PayPal approve URL (USD). Prefer for clear buy intent. Pass optional shipToCountry for soft shipping estimate. Single verified match → checkout immediately. Multiple → choices. Wait ~60s then poll getOrderStatus every 60s.

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": "quickCheckout"
  }
}

Input Schema

NameRequiredDescriptionDefault
needNoWhat they want, e.g. 3-month kit, bulk pack, filter
slugNoProduct slug alias
quantityNo
productIdNoProduct id or slug if already known
deviceQueryNoDevice model text, e.g. Roborock S7 or S7+
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

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses that the result is a hosted PayPal approve URL in USD, that a single verified match triggers immediate checkout while multiple matches return choices, and that the caller should wait ~60s before polling getOrderStatus. What it omits is the mutation profile — it never states plainly that an order is created, nor whether payment is captured here or only approved, and no auth/permission requirements are mentioned.

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?

The definition is front-loaded — 'ONE-SHOT' plus the verb and return value come first — and the telegraphic sentences carry distinct facts (return value, routing preference, match branching, polling cadence) with little filler. The clipped style ('Multiple → choices') is dense but readable; nothing is wasted, though a few fragments are terser than necessary.

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?

For a six-parameter, zero-required, annotation-free transaction tool with no output schema, the description covers the success path and the multi-match path well and explains what the return value is. It leaves a meaningful gap on the zero-match / resolution-failure case and on whether the 60s poll implies asynchronous order fulfillment, which an agent would need to set caller expectations correctly.

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 83%, so the schema already documents need, slug, productId, deviceQuery, and shipToCountry. The description's only parameter-level addition is that shipToCountry yields a 'soft shipping estimate', which the schema field description already says. It adds no guidance on precedence among need/slug/productId/deviceQuery or on what quantity means, so it does not materially exceed the schema baseline.

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?

The description opens with a concrete verb and outcome: 'resolve a verified-fit kit and return a hosted PayPal approve URL (USD)'. That is far more specific than the bare name 'quickCheckout' and tells an agent exactly what comes back. It stops short of naming the sibling createCheckout or explaining how this differs from it, so the sibling distinction is only implied by 'ONE-SHOT' and 'Prefer for clear buy intent'.

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?

There is a real usage signal — 'Prefer for clear buy intent' — plus a post-call protocol ('Wait ~60s then poll getOrderStatus every 60s'). However, the alternative createCheckout is never named, and no when-not-to-use condition (e.g., ambiguous intent, multi-item carts) is stated. An agent must infer the routing rule from the word 'Prefer'.

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