Skip to main content
Glama

Open a stripe-hosted card page

well_create_hosted_payment_link

Open a Stripe-hosted page for one of three card moments: add_card (a new card), recollect_card (a card group-3 of well_list_payment_cards saved by another person, which must be re-entered on this workspace's own Stripe customer before it can charge here), or complete_authentication (a bank's 3-D Secure check).

Returns url, a link on checkout.stripe.com, billing.stripe.com, hooks.stripe.com or invoice.stripe.com; expires_at, when the page stops working; and then, the tool to call once the user is back (well_list_payment_cards). Hand the url to the widget or open it; never type it into the conversation, never ask for or relay what the page itself collects (a card number, an expiry, a security code), and never read it back from a tool result — this tool returns no card data by design, so there is none to relay.

complete_authentication is refused with authentication_unavailable for now: Well holds no billing offer whose charge the page could finish. Give the bank-check link the payment receipt carries instead, or send the owner to the billing page.

Only a workspace owner or admin opens a hosted payment link. error_reason: missing_key (recollect_card without card_ref, or complete_authentication without offer_id), no_membership (the caller has no active membership in the workspace, or no workspace is in context), not_admin (the caller is a member but not an owner or an admin), authentication_unavailable (see above), billing_off (Well is free during the launch, so there is nothing to pay yet), no_customer (the workspace has no Stripe customer yet; send the owner to the billing page first), failed (Stripe did not return a session).

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
purposeYesadd_card: the workspace adds a new card. recollect_card: a card group-3 of `well_list_payment_cards` saved by another person must be re-entered on this workspace's own Stripe customer. complete_authentication: a bank's 3-D Secure check must finish before a charge or a saved card is usable.
card_refNoRequired for recollect_card: the opaque cardRef `well_list_payment_cards` gave for the card being re-entered.
offer_idNoRequired for complete_authentication: the offer_id of the billing offer that needs the bank check.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
urlNoA Stripe-hosted page. Open it as given; never read, repeat, log or store anything the page itself holds.
thenNoThe tool to call once the user says they are back from the page.
errorNo
successYes
expires_atNoWhen the page stops working, as an ISO timestamp; null when Stripe gave no expiry.
error_reasonNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / expires_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / expires_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive behavior, but the description adds substantial context: returned `url`, `expires_at`, and `then`; no card data is returned by design; permission constraints; and detailed `error_reason` meanings. The loose phrase “this read” is imprecise but does not substantively contradict the clear open/create semantics.

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 core action and the three modes, and the remaining sections are organized around returns, safety rules, refusals, permissions, errors, and workspace scoping. It is dense and lengthy, but most sentences earn their place given the tool’s complexity.

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

Completeness5/5

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

Even though an output schema exists, the description covers the operational context an agent needs: auth requirements, failure modes, security handling of the returned URL, and workspace-resolution behavior. There is no significant missing context for correct invocation.

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?

Schema description coverage is already 100%, so the schema carries most parameter semantics. The description still adds useful meaning by tying `card_ref` and `offer_id` to `missing_key`, explaining when `workspace_id` must be supplied, and clarifying the purpose enum in workflow terms.

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 opens with a specific verb and resource: it opens a Stripe-hosted page for one of three enumerated card moments. The three modes (`add_card`, `recollect_card`, `complete_authentication`) are clearly distinguished, so an agent can tell exactly what operation this tool performs.

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

Usage Guidelines5/5

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

It states the three valid scenarios, the owner/admin prerequisite, the direct-call case for a single-workspace token, and the `workspace_id` requirement when multiple workspaces are authorized. It also explicitly says `complete_authentication` is refused for now and points to alternatives, which is strong when-to-use/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