Skip to main content
Glama

Connect stripe

connect_stripe

Get a link the person opens to connect their own Stripe account, so clients pay the agency straight into it when they sign an agreement (agreement_draft, agreement_send). One click: a Google sign-in to their Agency Autopilot account if that browser isn't signed in, then Stripe's own page. The link lasts 30 minutes and works once. No key, password or token is ever typed into the conversation. Use it whenever an agreement says the agency's Stripe isn't connected.

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": "connect_stripe"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the constraints that actually matter for planning: the link is single-use, expires in 30 minutes, requires a Google sign-in to the user's account on that browser, and involves no secret ever being typed into the conversation. "Works once" also gives the agent the practical equivalent of the non-idempotent hint, which the annotation only states formally.

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

Conciseness4/5

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

The first sentence front-loads the outcome, then the mechanics (sign-in flow, 30-minute single use, no secrets) follow, and the closing sentence supplies the when-to-use. Each sentence carries distinct information, though "One click: a Google sign-in ... then Stripe's own page" is slightly narrative and could be a clause shorter.

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?

With no parameters and no output schema, the description does the heavy lifting well by explaining what the returned artifact is and how it behaves. The one residual ambiguity is whether the link is returned to the agent to hand to the client or delivered automatically, which matters for how the agent should follow up.

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?

The tool takes zero parameters, which is the baseline-4 case, and the description correctly implies nothing needs to be supplied. It adds no parameter-level detail because there is none to add; the surrounding narrative about the click-through flow is what substitutes for schema complexity.

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?

"Get a link the person opens to connect their own Stripe account" names a specific verb (retrieve a link) and a specific resource (Stripe account connection), and the resource name alone separates it from connect_google, connect_meta, connect_crm and connect_wordpress. It also states the downstream purpose (clients pay the agency directly once an agreement is signed), so an agent knows exactly what capability is being acquired.

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?

"Use it whenever an agreement says the agency's Stripe isn't connected" gives a concrete triggering condition, and the reference to agreement_draft / agreement_send situates it in the workflow. It does not name when NOT to use it or point at near-neighbours such as link_account, account_links or client_access_link, so the routing is clear in context but not exhaustive.

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.