Skip to main content
Glama

create_checkout

Create a Stripe-hosted checkout for one Agent Field Kit product and return its URL. Does NOT charge anything: a human, or an agent with explicit payment authority, must pay on the returned page. Prices: single template $29 (Agent Security Audit Kit $79), full kit of the 4 original templates $79, team license (10 users) $199. 14-day no-questions refunds. Also sold: Cyber Defense Bundle $79, Bundle + 1 year Cyber Desk Pro $199. Returns session_id and status_url; after payment call get_order with the session_id to receive signed download links (agent-to-agent purchase flow). Returns 'checkout_not_open' until checkout launches.

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": {
      "product_id": "<product_id>"
    },
    "name": "create_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoBuyer email for the receipt (optional)
agent_nameNoName of the purchasing agent/app (optional, analytics only)
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / product_id / enum
      Previous value: -[
      -  "cost-roi-calculator",
      -  "eval-test-plan",
      -  "incident-runbooks",
      -  "vendor-security-questionnaire",
      -  "afk-cyber-bundle-pro-year",
      -  "cyber-defense-bundle",
      -  "mcp-tool-access-review",
      -  "prompt-injection-test-pack",
      -  "agent-observability-starter",
      -  "agent-security-audit-kit",
      -  "realtime-agent-monitoring-kit",
      -  "ai-slop-editing-kit",
      -  "secrets-rotation-kit",
      -  "approval-gates-kit",
      -  "eu-ai-act-transparency-kit",
      -  "mcp-server-auth-kit",
      -  "agent-skill-authoring-kit",
      -  "ai-supply-chain-defense-kit",
      -  "inference-key-abuse-kit",
      -  "ci-registry-credential-kit",
      -  "oauth-grant-revocation-kit",
      -  "cyber-defense-dashboard-kit",
      -  "full-kit",
      -  "team-license"
      -]New value: +[
      +  "cost-roi-calculator",
      +  "eval-test-plan",
      +  "incident-runbooks",
      +  "vendor-security-questionnaire",
      +  "afk-cyber-bundle-pro-year",
      +  "cyber-defense-bundle",
      +  "mcp-tool-access-review",
      +  "prompt-injection-test-pack",
      +  "agent-observability-starter",
      +  "agent-security-audit-kit",
      +  "realtime-agent-monitoring-kit",
      +  "ai-slop-editing-kit",
      +  "secrets-rotation-kit",
      +  "approval-gates-kit",
      +  "eu-ai-act-transparency-kit",
      +  "mcp-server-auth-kit",
      +  "agent-skill-authoring-kit",
      +  "ai-supply-chain-defense-kit",
      +  "inference-key-abuse-kit",
      +  "ci-registry-credential-kit",
      +  "oauth-grant-revocation-kit",
      +  "cyber-defense-dashboard-kit",
      +  "agent-red-team-suite",
      +  "ai-spend-kill-switch-kit",
      +  "exposure-patch-alerts-kit",
      +  "full-kit",
      +  "team-license"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag this as a non-idempotent, open-world write; the description adds genuinely new behavior: no charge occurs here, 14-day refunds, a 'checkout_not_open' pre-launch state, and the returned session_id/status_url. Only idempotency/retry behavior is left to annotations, which is acceptable.

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?

Front-loaded with purpose, then constraints, return values, and the pre-launch edge case. The pricing/bundle enumeration is the weakest part — it reads as merchandising copy and lengthens the definition, though it is not filler for a shopping tool.

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?

With no output schema, the description correctly supplies the return shape (session_id, status_url) and the handoff to get_order. Payment authority, refund policy, and the unavailable state are all covered; little an agent needs is missing.

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 67%, and email/agent_name are already described in the schema. The description adds price mapping for a handful of product_id options ($29 single, $79 full kit, $199 team license), which helps selection, but covers only a fraction of the 27 enum values, so it does not fully compensate.

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+resource+scope: 'Create a Stripe-hosted checkout for one Agent Field Kit product and return its URL.' That distinguishes it immediately from the read-oriented siblings (get_product, search_products) and from get_order, which is named later in the flow.

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?

Explicitly states this does not charge and that a human or authorized agent must complete payment on the returned page, then prescribes the follow-up step ('after payment call get_order with the session_id'). It does not compare against other purchase-ish siblings, but the when/when-not and next-step routing are clear.

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