Skip to main content
Glama
r28ai

Sales Prep MCP

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

stripe_invoices_create

Create a draft Stripe invoice for a customer that bills nothing until finalized. Build the safe, unpaid half of invoicing before you charge.

Instructions

Create a draft invoice for a customer. It bills nothing until finalised, so this is the safe half of invoicing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
footerNoFooter text displayed on the invoice.
dueDateNoUnix timestamp when payment is due. Valid only when `collection_method` is 'send_invoice'. Seconds, not milliseconds: 1700000000, not 1700000000000.
currencyNoThree-letter lowercase ISO currency code. Absent, the customer's currency.
customerYesThe ID of the customer to bill.
metadataNoSet of key-value pairs attached to the invoice.
discountsNoCoupons and promotion codes to apply. Absent, the invoice inherits the customer's discount.
onBehalfOfNoThe connected account the funds are intended for. Its branding and support information appear on the invoice.
autoAdvanceNoWhether Stripe collects the invoice automatically. False leaves the invoice where it is until you act on it.
descriptionNoAn arbitrary string attached to the invoice. Shown as the memo in the Dashboard.
daysUntilDueNoDays until the invoice is due. Valid only when `collection_method` is 'send_invoice'.
subscriptionNoBill this subscription. The invoice then includes only that subscription's pending items, and its billing cycle is untouched.
collectionMethodNoHow to collect payment. Absent, Stripe charges the customer's default payment method.
statementDescriptorNoWhat the customer sees on their card statement. Must contain at least one letter.
defaultPaymentMethodNoThe payment method to charge. It must belong to the invoice's customer.
pendingInvoiceItemsBehaviorNoWhether to pull the customer's pending invoice items onto this invoice. Absent, Stripe excludes them and the draft is empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag a mutation (readOnlyHint false) and open-world scope; the description adds genuinely new behavioral context: the invoice does not bill until finalised, so creation itself is side-effect-free with respect to payment. It does not cover auth/permission needs or that a draft is empty without line items.

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 short sentences, front-loaded with the action and followed by the key behavioral reassurance. Nothing is wasted and nothing important is buried.

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?

For a 15-parameter mutation with no output schema, the description is thin: it omits the workflow detail that the draft is empty unless invoice items are added (via stripe_invoice_items_create) and says nothing about finalization as the follow-up step. The rich schema compensates on parameters, but the end-to-end workflow is incomplete.

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 15 parameters are already documented in the schema. The description adds no additional parameter meaning (e.g., defaults, interactions), which matches the baseline of 3 when the schema carries the load.

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 draft invoice for a customer.' The phrase 'the safe half of invoicing' nicely frames it as distinct from a finalization step, though it never names the sibling (stripe_invoices_finalize) explicitly.

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 when this is appropriate ('it bills nothing until finalised') which nudges the agent toward creating a draft before finalizing, but it never states prerequisites, when-not-to-use, or the alternative tool by name. Usage is inferable rather than explicit.

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