Skip to main content
Glama

Car Background AI

Create checkout link

create_checkout

Start a first subscription for a workspace that has none, e.g. when get_credits shows too few credits. Take price_id from list_plans; currency picks one of that plan's fixed local prices and buyer decides VAT handling for EU and UK buyers. This call charges nothing: it returns a Stripe checkout url for the user to open and pay, and the plan's photos are added once the payment completes. For a workspace that already subscribes it returns already_subscribed; use change_plan there instead. Needs an OAuth sign-in: with an API key it returns an error pointing to the app.

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

Input Schema

NameRequiredDescriptionDefault
buyerNoEU and UK buyers: `business` collects a VAT number (reverse charge), `personal` adds VAT.
currencyNoA key of the plan's `currency_options` (e.g. `eur`) to pay the fixed local price. Omit for USD.
price_idYesA `price_id` from list_plans.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, non-open-world write; the description adds substantial context beyond that: it charges nothing now, returns a Stripe checkout URL, and photos are provisioned only after payment completes. It also discloses the `already_subscribed` outcome and the OAuth-vs-API-key behavior. It stops short of describing URL expiry or session lifetime, so it is strong but not exhaustive.

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 the primary constraint (first subscription only) before parameters and behavior, and each sentence carries decision-relevant information. Slight overlap with the schema on `currency` and `buyer` keeps it from being maximally tight.

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

Completeness5/5

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

For a three-parameter mutation with no output schema, the description covers the trigger, the alternative path, the sourcing of IDs, the no-charge/redirect nature of the result, the post-payment side effect, and the auth requirement. An agent has everything needed to call it correctly or route elsewhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes further by telling the agent where `price_id` comes from (list_plans) and that `currency` selects among the plan's fixed local prices with USD as the default. The VAT implications of `buyer` largely restate the schema's enum description.

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 verb and resource ('Start a first subscription for a workspace that has none') and immediately bounds the scope to first-time subscriptions, which cleanly separates it from change_plan. The trigger condition (get_credits shows too few credits) makes the intent unmistakable.

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?

Gives explicit when-to-use (no existing subscription, low credits), when-not-to-use with the named alternative ('For a workspace that already subscribes ... use change_plan there instead'), and the prerequisite auth mode (OAuth required, API key errors out). Nothing is left to inference.

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