Skip to main content
Glama
Stripe Testing Tools MCP Server

Stripe Testing Tools MCP Server

by hideokamoto

Create Stripe Test Subscription

create_stripe_test_subscription

Create a new Stripe subscription for testing purposes. Specify a customer, price items, and optional payment method to generate realistic test subscription data.

Instructions

Create a new Stripe subscription for testing purposes

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": "<customer>",
      "items": "<items>"
    },
    "name": "create_stripe_test_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesA list of subscription items.
customerYesThe ID of the customer to create the subscription for.
payment_method_idNoThe payment method to use for the subscription
proration_behaviorNoDetermines how to handle prorations when the subscription items change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is already carried structurally. The description adds the meaningful signal that this operates in test mode, but says nothing about side effects an agent would care about: whether prorations trigger invoices, whether a payment method is required, or what happens on failure.

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

Conciseness4/5

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

A single short sentence with no filler, and the verb-plus-resource is front-loaded. It is efficient, though its brevity borders on under-specification rather than optimal density.

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?

With four fully documented parameters, an enum, and non-destructive write annotations, the structured data covers most of what an agent needs. The gap is behavioral: for a creation tool with billing implications, the description should note that it requires a test-mode context and existing customer/price IDs, and whether it can cause charges or invoices.

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 customer, items, payment_method_id, and the proration_behavior enum are all documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a new Stripe subscription') plus a scope qualifier ('for testing purposes'), so an agent immediately knows this creates a subscription rather than a clock, customer, or product. It does not explicitly differentiate itself from the sibling write tools beyond the noun, but the noun is unambiguous.

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?

'For testing purposes' implies this belongs in the test-mode tool cluster and should not be used against live data, which is mild contextual guidance. There is no statement of preconditions (customer must already exist, prices must exist) and no when-not-to-use or alternative-tool guidance.

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