Skip to main content
Glama
Stripe Testing Tools MCP Server

Stripe Testing Tools MCP Server

by hideokamoto

Create Stripe Test Customers

create_stripe_test_customers

Create one or more Stripe test customers with optional email, name, test clock, and payment method to support Stripe integration testing.

Instructions

Create one or more Stripe test customers for testing purposes

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_stripe_test_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe name of the customers
emailNoThe email of the customers
numberNoThe number of customers to create
test_clockNoThe ID of the test clock to associate with the customers
descriptionNoThe description of the customers
payment_method_idNoThe payment method to use for the customers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is known; the description adds that records are created in Stripe test mode rather than live, which is meaningful context. It omits other behavioral traits such as whether creation is idempotent, whether duplicate emails collide, rate limits, and what happens when number exceeds 1.

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 purpose is front-loaded. It is efficient but so terse that it borders on under-specification rather than being genuinely tight.

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

Completeness2/5

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

Six parameters, all optional, no output schema, and a mutation operation whose return value (the created customer objects) is never described. The most important open question for a tool that creates N customers from one name/email payload — whether duplicates are produced and what the response looks like — is left entirely to inference.

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 all six parameters are already documented in the schema, which sets the baseline at 3. The description only echoes the 'one or more' notion from the number parameter and does not clarify whether name/email/description are applied identically to every created customer or how payment_method_id and test_clock interact with bulk creation.

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 ... Stripe test customers') and scopes it to test data, which separates it from siblings like create_stripe_test_clock or create_stripe_test_subscription by resource name alone. It does not explicitly say why to choose this over those siblings, but the object being created 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?

There is no when-to-use guidance: nothing says this requires test-mode API credentials, nothing tells the agent to create a test clock first when simulating time, and no exclusions or alternatives are named. The only implied usage is 'for testing purposes', which the agent already knows from the tool name.

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