Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-upgradeSubscription

Idempotent

Upgrade a subscription by selecting hobby or startup tier, server quantity, and annual billing.

Instructions

POST /stripe.upgradeSubscription

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

Input Schema

NameRequiredDescriptionDefault
tierYes
isAnnualYes
serverQuantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so some of the burden is lifted, but the description adds nothing: no indication of billing/proration effects, whether a payment method is required, whether the change is immediate or at period end, or what happens to existing subscription state. The bare POST path conveys only that a mutation occurs.

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 that brevity is under-specification rather than conciseness, since the single token contributes no usable information beyond the tool name. Nothing is front-loaded because there is nothing substantive 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 required-parameter mutation with no output schema and only weak annotation coverage, an agent needs to know upgrade direction, cost implications, and parameter meaning. None of this is present, so the definition is inadequate to call the tool correctly.

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% and there are three required parameters (tier, serverQuantity, isAnnual). The description mentions none of them, so it does not compensate for the schema gap at all; the enum values and minimum=1 constraint are left entirely to the raw schema.

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.upgradeSubscription" only restates the tool name as an HTTP route. It implies an upgrade of a subscription but gives no statement of what is actually upgraded, and nothing distinguishes it from siblings like stripe-getCurrentPlan or stripe-createCheckoutSession that touch the same billing domain.

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 guidance, no prerequisites, and no mention of alternatives. An agent has no basis to choose this over stripe-createCheckoutSession or stripe-startFreeTrial.

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