Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-startFreeTrial

Idempotent

Starts a Stripe free trial for the chosen hobby or startup tier, letting users begin a trial subscription through Dokploy.

Instructions

POST /stripe.startFreeTrial

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": "stripe-startFreeTrial"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply only openWorldHint and idempotentHint; the description adds zero behavioral context. It does not say whether a payment method is required, whether the trial converts to a paid subscription, whether calling it twice is safe beyond the idempotent hint, or what the caller gets back.

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?

The text is short but that is under-specification rather than conciseness; a bare route string conveys no information beyond the tool name and does not front-load any actionable detail.

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 billing mutation with a required enum parameter, no output schema, and minimal annotations, the description should carry nearly all the explanatory burden and carries none. An agent cannot determine preconditions, side effects, or parameter meaning from this definition.

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?

One required parameter with 0% schema description coverage, and the description explains nothing about it. The enum values "hobby" and "startup" are left entirely undefined — no indication of what tier affects or how it interacts with the trial.

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?

"POST /stripe.startFreeTrial" only restates the tool name as an HTTP route; there is no verb+resource statement of what starting a free trial actually does (which subscription/plan, what the trial length is, what state changes). An agent can guess the general intent from the name, but the description itself adds nothing and gives no differentiation from siblings like stripe-upgradeSubscription or stripe-createCheckoutSession.

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

Usage Guidelines1/5

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

There is no when-to-use, when-not-to-use, or prerequisite guidance of any kind. Nothing indicates how this relates to stripe-upgradeSubscription, stripe-canCreateMoreServers, or any eligibility condition.

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