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

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Pay Invoice

pay_invoice
Destructive

Attempt to pay an open invoice using the default payment method, or specify a payment method to use.

Instructions

Attempt to pay an open invoice using the default payment method.

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "pay_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoice_idYesInvoice ID (in_...)
payment_methodNoSpecific payment method to use
idempotency_keyNoOptional idempotency key for safe retries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already indicate destructive behavior. Description adds that it attempts to pay an open invoice, but lacks details on success/failure scenarios, idempotency, or side effects.

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?

Single, front-loaded sentence with no wasted words. Every word adds value.

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?

Adequate for a tool with full schema coverage and destructive annotation, but lacks details on return behavior, error conditions, and when the invoice is not open.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage. Description implies default payment method behavior when payment_method param is omitted, adding context beyond 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?

Description clearly states the action (pay) and resource (invoice), and distinguishes from siblings like create_invoice, void_invoice, or finalize_invoice. The phrase 'open invoice' adds a precondition.

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 vs alternatives like finalize_invoice or void_invoice. No mention of prerequisites or exclusions.

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