Skip to main content
Glama

Connect the payment provider, read only

payments_connect
Read-only

Revenue share: Shipfound takes 30% of what each paying customer it brought pays in their first 12 months (the first one is free), charged to the founder's card and added to their balance for more work. To count those customers it reads the product's payment provider with a key that only reads. This says where the founder pastes it (the billing page, never this chat) and how to make it for provider (stripe or dodo; both when left out), plus the two things the product needs: its signups reported to Shipfound (/shipfound:users) and the person's own id passed at checkout. For an iOS app (provider appstore, the default in an app's space): an In-App Purchase key, and the change to ship in the app (a random id for the person, the Apple Ads token at first open, the same id on each purchase); a subscriber counts when their install came through an Apple Ads keyword Shipfound added. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "payments_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "stripe",
      -  "dodo"
      -]New value: +[
      +  "stripe",
      +  "dodo",
      +  "appstore"
      +]
  2. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds that the provider key is read-only and lists setup requirements, but it also mixes in revenue-share charging language that is unrelated to invocation behavior and does not clarify return values 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.

Conciseness2/5

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

The description is a long, dense run-on that front-loads revenue-share policy instead of the tool's action. Multiple parentheticals and setup details obscure the core invocation, and sentences do not consistently earn their place.

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?

It covers provider choices and substantial onboarding context, including signup reporting and checkout ID requirements. But for a tool named payments_connect with no output schema, it never clearly states what the tool returns or what happens after invocation, leaving a meaningful gap.

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?

Although schema description coverage is 0%, the description compensates well for the single provider parameter by explaining stripe and dodo, that both are used when omitted, and that appstore is the default in an app's space. It adds meaningful selection semantics beyond the enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description eventually states that the tool reads the product's payment provider with a read-only key, but this is buried under revenue-share and setup details. It does not open with a clear verb+resource statement such as 'Connect or inspect a payment provider,' and it never explicitly distinguishes the tool from siblings.

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 gives provider-specific guidance: stripe or dodo, both when omitted, and appstore for iOS apps where it is the default. However, it does not state when to use this tool versus alternatives, nor does it provide when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources