Skip to main content
Glama
Sign In
stripe-mcp-server

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cancel Subscription

cancel_subscription
Destructive

Cancel a subscription immediately or at the end of the current billing period. Optionally include cancellation reason and internal comment.

Instructions

Cancel a subscription immediately or at the end of the current period.

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": {
      "subscription_id": "<subscription_id>"
    },
    "name": "cancel_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscription_idYesSubscription ID (sub_...)
cancel_at_period_endNoIf true, cancel at period end instead of immediately (default: immediate)
cancellation_detailsNoCancellation details
idempotency_keyNoOptional idempotency key for safe retries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations indicate destructiveHint=true, and description adds timing nuance (immediate vs end of period). However, it does not disclose side effects like proration, refunds, or access loss.

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

Conciseness5/5

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

Single sentence, 11 words, front-loaded with action and key distinction. No wasted words.

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

Completeness3/5

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

No output schema. Description provides high-level purpose but lacks details on return values, confirmation, or consequences beyond the destructive annotation. Adequate for a simple tool but not fully complete.

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%, so description adds little beyond the schema. The description's mention of 'immediate or at the end of the current period' maps to cancel_at_period_end, but the schema already describes that parameter.

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?

Description uses verb 'Cancel' and resource 'subscription', clearly distinguishing two modes (immediate vs at period end). It uniquely identifies the tool among siblings like update_subscription or delete_customer.

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?

No guidance on when to use this tool versus alternatives (e.g., update_subscription for modifications). No when-not-to-use or prerequisite conditions provided.

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