Skip to main content
Glama

Create report checkout

create_report_checkout

Open Stripe Checkout for one $9.99 report. Returns a hosted checkout URL the human customer must open and pay. The agent must not pay and must not send card data. Email is optional. A checkout with no email is never reused. When a checkout is reused, the report token is not returned. After the customer pays, poll get_report.

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": {
      "vin": "<vin>"
    },
    "name": "create_report_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYes17-character VIN. The check digit is required.
emailNoOptional. Stripe Checkout collects an email when this is omitted. A checkout with no email is never reused.
sourceNoOptional agent name stored with the order. Sanitized and length-capped.

Output Schema

NameRequiredDescriptionDefault
order_idYes
referenceYes
expires_atYes
status_urlYes
checkout_urlYes
report_tokenNo
customer_instructionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond annotations by disclosing that the URL must be opened by a human, the payment restriction, and non-obvious reuse semantics (no-email checkouts are never reused; reused checkouts omit the report token), which concretely explains the idempotentHint=false flag. Missing only details like checkout expiry or what happens if a checkout is abandoned.

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?

Roughly five short sentences, front-loaded with the action and return value, then constraints, then the next step. Nothing extraneous; every clause conveys actionable information.

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?

An output schema exists, so return-value detail is not required, yet the description still names the hosted URL, which is the key output. Combined with the payment restriction and polling guidance, an agent has everything needed to invoke and follow up, though checkout lifetime/expiry behavior is unaddressed.

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 all three parameters are already documented, including the email reuse rule that the description restates. The description adds context (the $9.99 price, one-report scope) but no new per-parameter syntax or validation meaning, so baseline 3 applies.

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?

States a specific action and resource: opens Stripe Checkout for exactly one $9.99 report and returns a hosted URL. The scope (single report, fixed price, human-completed payment) sets it apart from sibling get_report and get_report_quote without needing their 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 defines agent boundaries (must not pay, must not send card data) and the follow-up path: after the customer pays, poll get_report. It also notes email is optional, so the agent knows it can call with only a VIN.

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