mcp-saas-toolkit

stripe_check_subscription

Check subscription status for a Stripe customer. Retrieve active subscriptions with plan details, billing period, and current status.

Instructions

Check the subscription status for a Stripe customer. Returns active subscriptions with plan details, billing period, and current status.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "stripe_check_subscription"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No	Filter by subscription status. Default: all	all
`customer_id`	Yes	The Stripe Customer ID (starts with cus_)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 29, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It states the return includes 'plan details, billing period, and current status', indicating a read operation, but does not disclose auth requirements, rate limits, or whether the operation may have side effects.

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?

The description consists of two concise, front-loaded sentences with no redundant information. Every word adds value.

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

Completeness4/5

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

Given the tool's simplicity (2 params, no output schema), the description adequately states what the tool returns. It could be enhanced by clarifying if the response is a single subscription or list, but overall complete for a check operation.

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% with clear descriptions for both parameters (customer_id and status). The description adds no additional parameter-specific meaning beyond what the schema already provides, so baseline 3 is appropriate.

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?

The description uses the specific verb 'check' with 'subscription status for a Stripe customer', clearly identifying the resource and action. It distinguishes from sibling tools like stripe_create_customer or stripe_list_customers by focusing on subscription status only.

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

Usage Guidelines3/5

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

The description implies the tool is used to retrieve subscription information but does not explicitly state when to use it versus alternatives (e.g., listing all subscriptions via other means) or any prerequisites. Usage is implied but no exclusions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.