Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

start_subscription_checkout

Generate a Stripe checkout URL so a user can subscribe to a Kiln paid tier (pro, business, or enterprise) with monthly or annual billing.

Instructions

Get a URL the user can visit to subscribe to a Kiln paid tier.

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": {
      "tier": "<tier>"
    },
    "name": "start_subscription_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierYes``"pro"``, ``"business"`` or ``"enterprise"`` — the plan to check out for.
emailNoPre-fill the Stripe email field. Optional. A signed-in caller's checkout is always for their own account's email; a different one is refused (``CHECKOUT_EMAIL_NOT_YOURS``).
billingNo``"monthly"`` or ``"annual"``. Default: "monthly".
cancel_urlNoWhere Stripe redirects on cancel. Defaults to the plans page on kiln3d.com. Same rule.
success_urlNoWhere Stripe redirects on success. Defaults to ``https://kiln3d.com/checkout/success?session_id={CHECKOUT_SESSION_ID}``. Must be an https address on kiln3d.com (``REDIRECT_NOT_KILN`` otherwise).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • changedInput schema / properties / billing / description
      Previous value: -"Default: \"monthly\"."New value: +"``\"monthly\"`` or ``\"annual\"``. Default: \"monthly\"."
    • addedInput schema / properties / cancel_url / description
      Added value: +"Where Stripe redirects on cancel.  Defaults to the plans page on kiln3d.com.  Same rule."
    • addedInput schema / properties / email / description
      Added value: +"Pre-fill the Stripe email field.  Optional.  A signed-in caller's checkout is always for their own account's email; a different one is refused (``CHECKOUT_EMAIL_NOT_YOURS``)."
    • addedInput schema / properties / success_url / description
      Added value: +"Where Stripe redirects on success.  Defaults to ``https://kiln3d.com/checkout/success?session_id={CHECKOUT_SESSION_ID}``. Must be an https address on kiln3d.com (``REDIRECT_NOT_KILN`` otherwise)."
    • addedInput schema / properties / tier / description
      Added value: +"``\"pro\"``, ``\"business\"`` or ``\"enterprise\"`` — the plan to check out for."
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the description only needs to add context. It does disclose one useful trait the annotations do not: the checkout is completed by the user visiting a returned URL, not inside the tool call. It says nothing about session expiry, authentication requirements, or that a Stripe session is created server-side.

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?

It is a single front-loaded sentence with no filler or redundancy. It is arguably terse to the point of under-specification, but nothing in it wastes space.

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

Completeness2/5

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

This is a billing-mutating tool with five parameters and no output schema, so the description should at least indicate that the return value is a URL to hand to the user and mention any expiry or one-time nature of the link. Neither appears, and the guidance a paying user's agent needs (existing subscriber vs new checkout) is absent.

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%, and the schema already explains tier values, the email ownership rule with CHECKOUT_EMAIL_NOT_YOURS, billing cadence, and the https/kiln3d.com redirect constraint with REDIRECT_NOT_KILN. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 sentence names a specific verb and resource ('Get a URL ... to subscribe'), so an agent knows it produces a link for a paid Kiln tier rather than performing the purchase. It does not differentiate from nearby billing siblings such as open_billing_portal, check_my_tier, or upgrade_kiln, so the agent must infer which one handles a new subscription.

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?

The phrase 'a URL the user can visit' implies an out-of-band, human-in-the-loop flow, which is usable context for deciding when to call this. However, there is no explicit statement of when to prefer it over check_my_tier or open_billing_portal, and no prerequisites such as being signed in or not already subscribed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools