Skip to main content
Glama

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Stripe Connector

stripe_connector
Read-onlyIdempotent

Stripe payments platform: account profile, charges, customers, payouts, balance transactions, refunds, disputes, and balance. Read-only via restricted API key (Path A). Phase 2A adds the reconciliation block: payouts, balance transactions, refunds, disputes, and balance — the primitives needed for QuickBooks-style payout reconciliation and Shopify-style settlement gap analysis. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesget_account: Get the authenticated Stripe account profile: business name, country, default currency, charges/payouts enabled status, | list_charges: List Stripe charges (payments) with cursor pagination. Returns charge id, amount (in smallest currency unit, e.g. cents) | list_customers: List Stripe customers with cursor pagination, optionally filtered by email. Returns customer id, email, name, descriptio | list_payouts: List Stripe payouts (bank settlements) with cursor pagination. Each payout represents money Stripe sent to the connected | get_payout: Get full detail for a single Stripe payout by id. Use to drill into one payout to inspect bank routing detail, automatic | list_balance_transactions: List Stripe balance transactions — the canonical Stripe ledger that every reconciliation tool uses to match every cent. | list_refunds: List Stripe refunds with cursor pagination. Each refund returns id (re_...), amount, currency, status (succeeded/pending | get_refund: Get full detail for a single Stripe refund by id. Returns amount, currency, status, reason, charge id, payment_intent id | list_disputes: List Stripe disputes (chargebacks) with cursor pagination. Each dispute returns id (du_...), amount, currency, status (w | get_dispute: Get full detail for a single Stripe dispute by id. Returns amount, status, reason, charge id, evidence_details with due_ | get_balance: Get the current Stripe balance snapshot — available funds (already cleared, eligible for payout), pending funds (not yet
paramsNoAction-specific parameters. get_account: none | list_charges: {limit?: integer, starting_after?: string, created_after?: integer} | list_customers: {limit?: integer, starting_after?: string, email?: string} | list_payouts: {limit?: integer, starting_after?: string, created_after?: integer, status?: string} | get_payout: {payout_id: string} | list_balance_transactions: {limit?: integer, starting_after?: string, created_after?: integer, type?: string, payout?: string} | list_refunds: {limit?: integer, starting_after?: string, created_after?: integer, charge?: string, payment_intent?: string} | get_refund: {refund_id: string} | list_disputes: {limit?: integer, starting_after?: string, created_after?: integer} | get_dispute: {dispute_id: string} | get_balance: none

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"get_account: Get the authenticated Stripe account profile: business name, country, default currency, charges/payouts enabled status,  | list_charges: List Stripe charges (payments) with cursor pagination. Returns charge id, amount (in smallest currency unit, e.g. cents) | list_customers: List Stripe customers with cursor pagination, optionally filtered by email. Returns customer id, email, name, descriptio"New value: +"get_account: Get the authenticated Stripe account profile: business name, country, default currency, charges/payouts enabled status,  | list_charges: List Stripe charges (payments) with cursor pagination. Returns charge id, amount (in smallest currency unit, e.g. cents) | list_customers: List Stripe customers with cursor pagination, optionally filtered by email. Returns customer id, email, name, descriptio | list_payouts: List Stripe payouts (bank settlements) with cursor pagination. Each payout represents money Stripe sent to the connected | get_payout: Get full detail for a single Stripe payout by id. Use to drill into one payout to inspect bank routing detail, automatic | list_balance_transactions: List Stripe balance transactions — the canonical Stripe ledger that every reconciliation tool uses to match every cent.  | list_refunds: List Stripe refunds with cursor pagination. Each refund returns id (re_...), amount, currency, status (succeeded/pending | get_refund: Get full detail for a single Stripe refund by id. Returns amount, currency, status, reason, charge id, payment_intent id | list_disputes: List Stripe disputes (chargebacks) with cursor pagination. Each dispute returns id (du_...), amount, currency, status (w | get_dispute: Get full detail for a single Stripe dispute by id. Returns amount, status, reason, charge id, evidence_details with due_ | get_balance: Get the current Stripe balance snapshot — available funds (already cleared, eligible for payout), pending funds (not yet"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "get_account",
-  "list_charges",
-  "list_customers"
-]New value: +[
+  "get_account",
+  "list_charges",
+  "list_customers",
+  "list_payouts",
+  "get_payout",
+  "list_balance_transactions",
+  "list_refunds",
+  "get_refund",
+  "list_disputes",
+  "get_dispute",
+  "get_balance"
+]
    • changedInput schema / properties / params / description
      Previous value: -"Action-specific parameters. get_account: none | list_charges: {limit?: integer, starting_after?: string, created_after?: integer} | list_customers: {limit?: integer, starting_after?: string, email?: string}"New value: +"Action-specific parameters. get_account: none | list_charges: {limit?: integer, starting_after?: string, created_after?: integer} | list_customers: {limit?: integer, starting_after?: string, email?: string} | list_payouts: {limit?: integer, starting_after?: string, created_after?: integer, status?: string} | get_payout: {payout_id: string} | list_balance_transactions: {limit?: integer, starting_after?: string, created_after?: integer, type?: string, payout?: string} | list_refunds: {limit?: integer, starting_after?: string, created_after?: integer, charge?: string, payment_intent?: string} | get_refund: {refund_id: string} | list_disputes: {limit?: integer, starting_after?: string, created_after?: integer} | get_dispute: {dispute_id: string} | get_balance: none"
  6. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: restricted API key auth, the 15-minute single-user provenance_token handoff with replica portability, and the unverified_model_data fallback labeling. Much of the remaining text (attribution footer, data-accuracy contract) is generic policy rather than tool-specific behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the body is long and padded with cross-cutting boilerplate (attribution footer handling, generic data-accuracy contract) that is not specific to invoking this connector. The chart_render/provenance instructions, while relevant, occupy the majority of the 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?

For a read-only multi-action connector with no output schema, the enum descriptions cover return fields per action, and the description covers scope, auth, and the provenance handoff. Pagination/response shape and the stripe_dashboard boundary are the notable gaps.

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% and the action enum carries per-action parameter and return-field detail, so the schema does the heavy lifting. The description only restates the resource categories and adds no syntax, format, or constraint detail beyond what the schema already documents.

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?

The opening sentence names a specific platform and enumerates the concrete resources covered (charges, customers, payouts, balance transactions, refunds, disputes, balance), which maps cleanly onto the action enum. However, it never differentiates itself from close siblings such as stripe_dashboard, quickbooks_connector, or shopify_dashboard, leaving the agent to infer the boundary.

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?

It states a read-only/restricted-key posture and a reconciliation use case (QuickBooks-style payout reconciliation, Shopify-style settlement gaps), and gives explicit routing guidance to chart_render for visuals. But it offers no when-not-to-use guidance and no comparison against the sibling dashboard/connector tools that cover overlapping payment data.

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

All CorpusIQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources