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

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Customer

create_customer

Create a Stripe customer record with optional email, name, phone, description, and metadata. Supports attaching a payment method and idempotency key for safe retries.

Instructions

Create a new Stripe customer with optional email, name, phone, description, and metadata.

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_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoCustomer email address
nameNoCustomer full name
phoneNoCustomer phone number
descriptionNoInternal description
metadataNoKey-value metadata pairs
payment_methodNoPayment method ID to attach
idempotency_keyNoOptional idempotency key for safe retries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden. It mentions creation but omits important traits like idempotency (despite idempotency key parameter), authentication needs, rate limits, or return value. The idempotency key parameter hints at safe retries, but description doesn't explain.

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?

The description is one concise sentence, efficient and front-loaded. However, it could be slightly more structured by listing all optional fields or mentioning idempotency. Minor improvement possible.

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?

Given 7 parameters, no annotations, and no output schema, the description is minimal. It doesn't explain the creation process, prerequisites, response structure, or differentiate from siblings like search_customers or update_customer. Incomplete for a tool with complex context.

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 each parameter is already described. The tool description lists only a subset of fields (email, name, phone, description, metadata) and omits payment_method and idempotency_key. It adds no new semantics beyond the schema, warranting baseline 3.

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 clearly states 'Create a new Stripe customer' with specific verb and resource, and lists optional fields (email, name, phone, description, metadata). It distinguishes from sibling tools like delete_customer and update_customer.

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 usage when you need to create a customer, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among the many sibling tools.

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