Skip to main content
Glama

Stripe_connect

by io.github.pipeworx-io

Stripe Get Customer

stripe_get_customer
Read-onlyIdempotent

Get a Stripe customer by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer ID (cus_...)
_apiKeyYesStripe secret or restricted API key (sk_...)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoCustomer ID
nameNoCustomer name
emailNoCustomer email
phoneNoCustomer phone
objectNoObject type (customer)
addressNoCustomer address
balanceNoAccount balance in cents
createdNoCreation timestamp
currencyNoCustomer currency
discountNoApplied discount
livemodeNoLive mode indicator
metadataNoCustom metadata
shippingNoShipping address
delinquentNoAccount delinquent status
tax_exemptNoTax exempt status
test_clockNoTest clock ID
descriptionNoCustomer description
default_sourceNoDefault payment source ID
invoice_prefixNoInvoice prefix
invoice_settingsNoInvoice settings
preferred_localesNoPreferred locales

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": {
+    "address": {
+      "description": "Customer address",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "balance": {
+      "description": "Account balance in cents",
+      "type": "integer"
+    },
+    "created": {
+      "description": "Creation timestamp",
+      "type": "integer"
+    },
+    "currency": {
+      "description": "Customer currency",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "default_source": {
+      "description": "Default payment source ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "delinquent": {
+      "description": "Account delinquent status",
+      "type": "boolean"
+    },
+    "description": {
+      "description": "Customer description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "discount": {
+      "description": "Applied discount",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "email": {
+      "description": "Customer email",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Customer ID",
+      "type": "string"
+    },
+    "invoice_prefix": {
+      "description": "Invoice prefix",
+      "type": "string"
+    },
+    "invoice_settings": {
+      "description": "Invoice settings",
+      "type": "object"
+    },
+    "livemode": {
+      "description": "Live mode indicator",
+      "type": "boolean"
+    },
+    "metadata": {
+      "description": "Custom metadata",
+      "type": "object"
+    },
+    "name": {
+      "description": "Customer name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "object": {
+      "description": "Object type (customer)",
+      "type": "string"
+    },
+    "phone": {
+      "description": "Customer phone",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "preferred_locales": {
+      "description": "Preferred locales",
+      "type": "array"
+    },
+    "shipping": {
+      "description": "Shipping address",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "tax_exempt": {
+      "description": "Tax exempt status",
+      "type": "string"
+    },
+    "test_clock": {
+      "description": "Test clock ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-stripe_connect-api-key",
+    "id": "cus_ABC123"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false. The description adds no additional behavioral context beyond stating the action, so it does not enhance transparency.

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?

The description is a single, efficient sentence with no wasted words. It is front-loaded and to the point.

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 output schema existence and comprehensive annotations, the minimal description is sufficient for a simple get-by-ID tool. It lacks mention of edge cases but is complete enough for typical use.

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%, with both parameters adequately documented. The description does not add meaning beyond the schema, meeting the baseline but not exceeding it.

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 'Get a Stripe customer by ID' uses a specific verb and resource, clearly distinguishing it from sibling tools like stripe_list_customers or stripe_get_balance.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., stripe_list_customers for multiple customers). The description implies usage when an ID is available, but lacks exclusions or context.

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