Skip to main content
Glama
CSOAI-ORG

Stripe Billing MCP

by CSOAI-ORG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cancel_subscription

Cancel a Stripe subscription by ID. Set whether to end now or at the billing period close and whether to prorate the final invoice.

Instructions

Cancel a Stripe subscription.

Args: subscription_id: Stripe subscription ID (sub_...) at_period_end: If True, cancel at end of billing period (default). If False, cancel immediately. prorate: Whether to prorate the final invoice (default True)

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results. Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNo
prorateNo
at_period_endNo
subscription_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it falsely claims 'read-only', 'no side effects', and 'idempotent' for a tool that cancels a subscription. This is actively misleading and sets false expectations about side effects, authentication, and rate limits.

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 description is long and repetitive, with a 'Behavior' section and a 'Behavioral Transparency' section duplicating the same false claims. Much of the content is irrelevant to cancellation and should be removed.

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 mutating tool with no output schema and no annotations, the description must explain actual side effects, errors, and results. It instead claims there are no side effects and gives generic analysis-tool boilerplate, leaving an agent completely unprepared for the real behavior of canceling a subscription.

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?

The Args section provides useful semantics for subscription_id, at_period_end, and prorate that go beyond the raw schema. However, api_key is left undocumented, and the surrounding false behavioral claims undermine trust in the parameter descriptions.

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 opening phrase 'Cancel a Stripe subscription' is clear, but the Behavior section immediately claims the tool is read-only and produces analysis output, directly contradicting the stated purpose. An agent cannot reliably determine whether this cancels a subscription or performs analysis.

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?

The 'When to use' section recommends using this tool for structured analysis or classification, which is irrelevant and misleading for a subscription cancellation tool. No guidance is given on when to cancel versus using sibling tools like create_subscription or list_invoices.

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