Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-createCheckoutSession

Creates a Stripe checkout session for a Dokploy plan by specifying tier, product ID, server quantity, and annual or monthly billing.

Instructions

POST /stripe.createCheckoutSession

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>",
      "productId": "<productId>",
      "serverQuantity": "<serverQuantity>",
      "isAnnual": "<isAnnual>"
    },
    "name": "stripe-createCheckoutSession"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierYes
isAnnualYes
productIdYes
serverQuantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

The only annotation is openWorldHint=true, which signals external side effects but explains nothing. The description adds no behavioral context for a mutation that presumably creates a billable Stripe checkout session — no note on what the caller receives (a session URL?), whether it charges immediately, or what tier/productId combinations are valid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but brevity here is under-specification rather than efficiency: a single route string conveys no actionable information beyond the tool name. Nothing is front-loaded because there is nothing to front-load.

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

Completeness1/5

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

For a payment-adjacent creation tool with four required inputs, no output schema, and minimal annotations, the definition is far too thin. An agent has no basis to choose valid parameter values or anticipate what the call returns or costs.

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

Parameters1/5

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

Schema description coverage is 0% across four required parameters (tier, productId, serverQuantity, isAnnual), and the description compensates for none of it. An agent cannot tell from the definition whether serverQuantity interacts with tier, or which productId corresponds to which tier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only restates the tool name as an HTTP route ("POST /stripe.createCheckoutSession"), so the verb and resource are derived entirely from the identifier. It gives no statement of what a checkout session is used for or what it produces, making it a tautology rather than a purpose statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites, and no pointer to alternatives such as stripe-upgradeSubscription, stripe-startFreeTrial, or stripe-createCustomerPortalSession. The agent must infer the selection criteria entirely from sibling names.

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