mcp-saas-toolkit

stripe_create_customer

Create a new Stripe customer by providing email, name, phone, and optional metadata. Returns the created customer object.

Instructions

Create a new Stripe customer with name, email, phone, and optional metadata. Returns the created customer object.

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": {
      "email": "<email>"
    },
    "name": "stripe_create_customer"
  }
}

Input Schema

Name	Required	Description
`name`	No	Customer full name
`email`	Yes	Customer email address
`phone`	No	Customer phone number
`metadata`	No	Key-value pairs for custom metadata (max 50 keys)
`description`	No	Internal description/notes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Indicates it creates a customer (write operation) and returns the created object. However, no annotations provided, and description lacks details on side effects, idempotency, rate limits, or permissions. Basic transparency but not comprehensive.

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?

Two sentences, front-loaded with the action and resource. Every word adds value; no redundancy.

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?

No output schema, but description states it returns the created object. For a tool with 5 parameters and no output schema, the description is adequate but lacks details on error handling or idempotency.

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 coverage is 100%, so the schema already describes all parameters. The description adds that metadata is optional but does not provide additional meaning beyond the schema.

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 the verb 'create', the resource 'Stripe customer', and lists the fields (name, email, phone, metadata). It distinguishes from sibling tools like stripe_list_customers which list customers.

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?

No guidance on when to use this tool versus alternatives (e.g., other Stripe creation tools like stripe_create_invoice). No prerequisites or when-not-to-use instructions.

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