Skip to main content
Glama

Stripe_connect

by io.github.pipeworx-io

Stripe List Charges

stripe_list_charges
Read-onlyIdempotent

List Stripe payment charges for your account, optionally filtered by customer ID. Returns charge ID, amount, currency, status, and timestamp. Supports limit (1-100) pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (1-100, default 10)
_apiKeyYesStripe secret or restricted API key (sk_...)
customerNoFilter by customer ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoAPI endpoint URL
dataNoArray of charge objects
objectNoObject type (list)
has_moreNoWhether more results exist

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Array of charge objects",
+      "items": {
+        "properties": {
+          "amount": {
+            "description": "Charge amount in cents",
+            "type": "integer"
+          },
+          "amount_captured": {
+            "description": "Amount captured in cents",
+            "type": "integer"
+          },
+          "amount_refunded": {
+            "description": "Amount refunded in cents",
+            "type": "integer"
+          },
+          "application": {
+            "description": "Application ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "application_fee": {
+            "description": "Application fee ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "application_fee_amount": {
+            "description": "Application fee amount",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "balance_transaction": {
+            "description": "Balance transaction ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "billing_details": {
+            "description": "Billing details",
+            "type": "object"
+          },
+          "captured": {
+            "description": "Charge captured",
+            "type": "boolean"
+          },
+          "created": {
+            "description": "Creation timestamp",
+            "type": "integer"
+          },
+          "currency": {
+            "description": "Currency code",
+            "type": "string"
+          },
+          "customer": {
+            "description": "Customer ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Charge description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "destination": {
+            "description": "Destination account",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "dispute": {
+            "description": "Dispute ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "disputed": {
+            "description": "Under dispute",
+            "type": "boolean"
+          },
+          "failure_balance_transaction": {
+            "description": "Failure balance transaction",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "failure_code": {
+            "description": "Failure code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "failure_message": {
+            "description": "Failure message",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fraud_details": {
+            "description": "Fraud details",
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Charge ID",
+            "type": "string"
+          },
+          "invoice": {
+            "description": "Invoice ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "livemode": {
+            "description": "Live mode",
+            "type": "boolean"
+          },
+          "metadata": {
+            "description": "Custom metadata",
+            "type": "object"
+          },
+          "object": {
+            "description": "Object type (charge)",
+            "type": "string"
+          },
+          "outcome": {
+            "description": "Outcome details",
+            "type": "object"
+          },
+          "paid": {
+            "description": "Charge paid",
+            "type": "boolean"
+          },
+          "payment_intent": {
+            "description": "Payment intent ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "payment_method": {
+            "description": "Payment method ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "payment_method_details": {
+            "description": "Payment method details",
+            "type": "object"
+          },
+          "receipt_email": {
+            "description": "Receipt email",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "receipt_number": {
+            "description": "Receipt number",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "receipt_url": {
+            "description": "Receipt URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "refunded": {
+            "description": "Charge refunded",
+            "type": "boolean"
+          },
+          "refunds": {
+            "description": "Refunds list object",
+            "type": "object"
+          },
+          "review": {
+            "description": "Review ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "shipping": {
+            "description": "Shipping details",
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "source": {
+            "description": "Payment source",
+            "type": "object"
+          },
+          "source_transfer": {
+            "description": "Source transfer ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "statement_descriptor": {
+            "description": "Statement descriptor",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "statement_descriptor_suffix": {
+            "description": "Statement descriptor suffix",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "Charge status",
+            "type": "string"
+          },
+          "transfer_data": {
+            "description": "Transfer data",
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "transfer_group": {
+            "description": "Transfer group",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "description": "Whether more results exist",
+      "type": "boolean"
+    },
+    "object": {
+      "description": "Object type (list)",
+      "type": "string"
+    },
+    "url": {
+      "description": "API endpoint URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-stripe_connect-api-key",
+    "limit": 25
+  },
+  {
+    "_apiKey": "your-stripe_connect-api-key",
+    "customer": "cus_ABC123",
+    "limit": 10
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds that it returns specific fields and supports pagination, which is useful but not extensive. No contradiction.

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 concise sentences with front-loaded purpose. Every word is relevant and efficiently conveys key information without extraneous text.

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

Completeness4/5

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

Given the presence of output schema and clear annotations, the description covers purpose, filter, pagination, and return fields. Missing details like status meanings are likely in the output schema, making it complete enough for a list tool.

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 baseline is 3. The description repeats information already in the schema (limit range, default; customer filter) without adding new semantic context. Adequate but not enhanced.

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 tool lists Stripe charges, specifies optional filter by customer ID, and mentions return fields. It distinguishes from sibling tools like stripe_list_customers and stripe_list_invoices by focusing on charges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates when to use the tool (to list charges) and mentions optional filtering and pagination. It does not explicitly contrast with alternatives, but the context is clear for a simple list tool.

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

All Stripe_connect toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

The set has several near-duplicate entry points: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, while ask_pipeworx_grounded/deep_research and bet_research/polymarket_edges overlap heavily. Verbose descriptions help in isolation, but an agent must choose between many similar-looking research and prediction-market tools before it can act.

Naming Consistency2/5

Naming mixes bare verbs (remember, forget, subscribe), prefixed families (pipeworx_*, polymarket_*, stripe_*), and descriptive noun-style names (entity_profile, validate_claim) with no single verb_noun pattern. Each cluster is internally consistent, but the overall set is unpredictable.

Tool Count2/5

37 tools is excessive for a server named Stripe_connect, especially since only 6 tools are actually Stripe-related and the rest are a sprawling Pipeworx data-research and prediction-market stack. The count would be heavy even for the broad research domain, and it is a serious scope mismatch for the stated name.

Completeness1/5

For the Stripe domain implied by the server name, the surface is severely incomplete: it is read-only (get/list) with no way to create customers, take payments, issue refunds, update invoices, or manage subscription lifecycles. The non-Stripe research tools are broad, but that does not fill the payment workflow gap.

Resources