Skip to main content
Glama

Create Checkout Link

create_checkout_session

Accepts doola's Terms of Service (https://www.doola.com/terms-of-service) for the Starter package on the user's behalf and creates the Stripe checkout for the formation. Show the user the Terms of Service and send termsAccepted: true only once they agree. Returns pricing (the first-year list price: quote pricing.summary VERBATIM and never call it 'charged today'), chargeSummary (what Stripe charges today after any discount: quote it VERBATIM), checkoutUrl (paste it verbatim into your reply, never a placeholder), checkoutSessionId (what verify_payment checks), and companyId / companyName (the company being paid for: name it to the user). Refused with PRECONDITIONS_NOT_MET until start_formation has saved the name, country and company name. Formation flow, in order: start_formation, create_checkout_session, verify_payment, save_company_details (industries from search_industries), submit_formation. Each response's nextStep is the step the flow now waits on.

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
termsAcceptedNotrue only after the user has seen the Terms of Service link and agreed to it.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Output Schema

NameRequiredDescriptionDefault
codeNoStructured error code when error=true (e.g. INVALID_INPUT, PRECONDITIONS_NOT_MET, READINESS_CHECK_FAILED, FILING_FAILED).
errorNotrue if the call failed
savedNoWhat this call saved.
messageNoHuman-readable status.
missingNoPrerequisites still unmet, in flow order. Empty when only filing remains.
pricingNoFirst-year list price. Quote `summary` verbatim; never call it 'charged today'.
nextStepNoThe step the formation flow now waits on; null once formation is complete.
companyIdNoThe company the call acted on.
checkoutUrlNoStripe checkout link. Paste it verbatim into the reply.
companyNameNoName of the company the call acted on. Name it to the user.
nextQuestionNoThe customer-facing question for nextStep; null once formation is complete.
chargeSummaryNoWhat Stripe charges today, after any discount. Quote it verbatim.
conversation_idNoThis conversation's handle. Pass it unchanged as conversation_id on every later call.
checkoutSessionIdNoPass it to verify_payment once the user has paid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / message / description
      Previous value: -"Human-readable status or instruction."New value: +"Human-readable status."
    • removedOutput schema / properties / nextAction
      Removed value: -{
      -  "description": "Imperative for the agent — follow verbatim.",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / nextActionInput
      Removed value: -{
      -  "description": "{tool, arguments} template for the next call. Replace every <placeholder> in arguments with the user's real answer.",
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • changedOutput schema / properties / nextQuestion / description
      Previous value: -"Question to ask the user verbatim before the next call."New value: +"The customer-facing question for nextStep; null once formation is complete."
    • changedOutput schema / properties / nextStep / description
      Previous value: -"The tool to call next; null when the flow is complete."New value: +"The step the formation flow now waits on; null once formation is complete."
    • addedOutput schema / properties / nextStep / properties
      Added value: +{
      +  "description": {
      +    "description": "Where the customer stands at this step and what their options are.",
      +    "type": "string"
      +  },
      +  "missingFields": {
      +    "description": "Arguments of that tool the step still needs.",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "tool": {
      +    "description": "The tool that records this step.",
      +    "type": "string"
      +  }
      +}
    • changedOutput schema / properties / nextStep / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "object",
      +  "null"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id
      Added value: +{
      +  "description": "This conversation's handle. Pass it unchanged as conversation_id on every later call.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, non-destructive, open-world write. The description goes further: it acts on the user's legal behalf, it can be refused with a named error code, and it enumerates what the response contains and how each field must be presented (quote pricing.summary and chargeSummary verbatim, never say 'charged today', paste checkoutUrl verbatim, never a placeholder).

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 action and the consent gate, then the response contract, then preconditions and flow order. Dense and mostly earning its place, though the return-field instructions are numerous enough to verge on a checklist rather than a description.

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 mutation tool in a multi-step flow, this covers consent requirements, failure mode, prerequisite step, downstream step, and how to present each returned field. An output schema exists, so the return-value detail is bonus rather than obligation, and no calling decision is left unresolved.

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, but the description adds a real semantic constraint beyond the schema: send termsAccepted: true only once the user has seen the ToS link and agreed. The analytics-only parameters are not elaborated, but the schema already covers them.

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: it accepts the Terms of Service for the Starter package and creates the Stripe checkout for the formation. That is clearly distinct from siblings like verify_payment, submit_formation and start_formation, which are named in the same breath.

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?

Explicit preconditions are given (refused with PRECONDITIONS_NOT_MET until start_formation has saved name, country and company name), the gating condition for termsAccepted is stated, and the tool's position in the ordered flow is spelled out with the next step named. Nothing about when to call it 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.